Celery worker alert: no completed work recorded for 1175 seconds, past 300-second threshold
On October 26, 2026 at 06:20, a 'Worker heartbeat stale' alert fired for a Celery worker, indicating the process was running but not processing work as expected. The last AgentRun was recorded 1175 seconds earlier, nearly four times the 300-second warning threshold. The alert suggested reading logs via docker logs and restarting the worker if it was looping, but the source does not state which action was taken or how the issue was resolved. The cause of the stall is not identified from the alert alone. The author concludes that liveness checks are insufficient and that alerts should track time since the last completed unit of work.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in