Job Errors
Structured job-error states from the dispatcher taxonomy. Each row represents a scan job that has been classified by error class and category. Operators can triage individual rows, apply repair actions, and bulk-fail terminal errors from this page.
How to
Triage an active error
- Find the error in the table (filter by class or category as needed)
- Click the Triage button to open the per-state detail view
- Review the context JSON and repair history
- Select a repair action and click Apply
Bulk-fail multiple errors
- Check the rows you want to terminal-fail
- Click "Bulk Fail" in the selection bar
- Confirm the dialog — this action is irreversible
Gotchas
- Fail is terminal — once applied, the job cannot be retried. Use redispatch to return a job to the pool.
- The category cards show zero counts in v1. Use the table filters to narrow by category.
- Per-class drilldown pages are accessible by clicking an error class chip in the table.
API calls (4)
| Method | Path | Description |
|---|---|---|
| GET | /api/health/job-errors | List active job error states |
| GET | /api/health/job-errors/:stateId | Single error state with repair history |
| POST | /api/health/job-errors/:stateId/repair | Apply a repair action |
| POST | /api/health/job-errors/bulk-repair | Bulk repair multiple states |
Related
- Alarms — Higher-level fault tracking via rule-based alarms
- Scanner Status — Per-scanner heartbeat and liveness status
- Scanners — Configure scanners and view their active errors
- No Scanner — Class detail
- Failed Scanner Auth — Class detail
- Scanner Disabled — Class detail
- Scanner IP Changed — Class detail
- No Heartbeat — Class detail
- Binary Version Mismatch — Class detail
- Stuck Pending — Class detail
- Stuck Running — Class detail
- Dispatcher Failure — Class detail
- Expired — Class detail
- Result Submit Failed — Class detail
- Scan Deleted — Class detail
- Target Invalid — Class detail
- Rate Limit Exhausted — Class detail