Stuck Pending
A scan job has sat in pending status without being claimed for more than 15 minutes. The dispatcher has not handed it to any scanner.
How to
Diagnose
- Confirm at least one scanner is heartbeating and active
- Check the scanner_id field on the job — if a specific scanner was targeted, that scanner may be down
- Check Health > Services > Dispatcher to confirm the dispatcher is running
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 the job if it is no longer needed
Gotchas
- Redispatch re-pends the job to its SAME scanner (scanner_id is not changed) — the dispatcher re-claims it on its next cycle. To move the job to a different scanner, use the separate reassign action (not available for this class).
- If ALL scanners are offline, redispatch will not help — fix the scanner fleet first.
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=redispatch | fail |
Related
- Job Errors Overview — Category model