Closed db-2001 closed 2 months ago
the "30000ms" timeout means that is timeout value, not that it did. If it actually timed out, it would say so. The checkjobs running on startup was an old issue, that was actually a bug, now you can see it will be 24 minutes before the next job is scheduled to run.
So nothing is actually broken :)
Ah, gotcha, good to know we're cleaning up start up behavior
👍🏼 Somewhere the export of jobs to files got lost, so on startup all the jobs would run, as they were scheduled weeks ago
What is broken?
Starting the latest cuttingedge image, I notice that the chromium browser doesn't download and times out immediately. Normally I see a bunch of check jobs but that doesn't seem to be happening.
Log-output
No response
Additional stuff