Stuck-task reconciliation
Tasks started forever. Fixed, automatically.
A background worker sweeps tasks stuck in started/pending past a configurable threshold, asks the agent to probe the engine's result backend, and applies the authoritative state back with a task.reconciled audit row.
The related dashboard view, captured with sample project data. Open the live demo to try it.
Ships with
- Authoritative probes for Celery, RQ, arq, Huey, and taskiq where their result backends are configured; Dramatiq currently reports unknown because a message id alone lacks actor and queue context
- Engine-matched routing: reconcile calls go to an agent that actually runs that engine
- Source-anchored state updates (agent cannot spoof engine / task_id)
- Rate-limited to protect the broker and audit log
Related