kanban-stuck-task-recovery

You can recover stuck Kanban tasks by diagnosing worker status, claim_expires, and dispatcher issues using a SQL reset script. This Skill executes the script to reclaim stale in_progress tasks and restore normal workflow operations.

Kanban tasks get stuck due to dead worker processes, expired claim_expires timestamps, or dispatcher outages. This Skill performs root cause analysis to identify dispatcher issues, worker crashes, and reclaim logic gaps causing the blockage.

The best way to prevent stuck Kanban tasks is preventive monitoring that checks for orphans and ready tasks. This Skill monitors cron jobs for status and suggests corrective actions to catch dispatcher issues and expired claims early.

Yes, resolving stuck Kanban tasks requires access to the Kanban database to execute the SQL reset script. You also need access to cron jobs for executing preventive monitoring and checking task status.

You reset and reclaim stale in_progress tasks by executing a SQL reset script against the Kanban database. This requeues tasks affected by expired claim_expires or dead workers, allowing active workers to reclaim them.