Pain point · Reliability & bugs · Causes churn
Single schedule becomes inaccessible and stops running
2 source threads · first seen 2021-08 · last seen 2024-12
Summary
A schedule page returns a gateway timeout and the CLI describe command fails, with no server errors logged. The affected schedules also no longer run, and upgrading did not help.
- Affects
- Self-hosters on Postgres using the auto-setup image
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The schedules do not run anymore either”
“After running for a period of time, the worker cannot get the corresponding task”