Dispatcher Failure
A job was assigned to a scanner but never transitioned to running. The hand-off between dispatcher and scanner did not complete within 5 minutes.
How to
Diagnose
- Check whether the assigned scanner is heartbeating and healthy
- Review scanner logs for fetch errors or restarts during the assignment window
Repair
- Redispatch — sets the job back to pending on the SAME scanner (scanner_id is kept); the dispatcher re-claims it on its next cycle
- Or fail if the job is stale
Gotchas
- A scanner that restarts after assignment but before start typically resolves itself when it picks back up — this class only fires after the threshold.
- If many jobs hit dispatcher_failure on the same scanner, that scanner has a deeper issue (fetch endpoint failing, network).
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=redispatch | fail |
Related
- Job Errors Overview — Category model