-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crons: check-ins did not time out. #3104
Comments
Hi @JeremiaAu Thanks for the report. We recently changed how we check for failures, and we forgot to have the consumers run in self hosted. Really sorry for the inconvenience here. JFYI, this is unrelated to your other report where the environments are duplicated. Here's the fix #3106 You could apply this locally to fix your problem, and I will also discuss getting a hot fix out with our self-hosted team. |
I just applied the fix and can confirm that it solves the issue. |
Self-Hosted Version
24.5.0
CPU Architecture
x86_64
Docker Version
26.1.3
Docker Compose Version
2.27.0
Steps to Reproduce
Expected Result
Check-ins time out after the configured amount of time.
Actual Result
(There are two identical timelines because of another issue: #3161, they might be related)
Event ID
No response
The text was updated successfully, but these errors were encountered: