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.
z4j dashboard — Stuck-task reconciliation
Mockup of the dashboard view for this feature. Live-reloading and themed to match your dashboard.
Ships with
- Covers every engine (Celery AsyncResult, RQ Job, arq Job.status, Huey result store, taskiq result_backend, Dramatiq Results middleware)
- 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