Expired
A job has been alive longer than the maximum allowed lifetime (24 hours by default) without reaching a terminal state. This is the safety net for jobs no other class catches.
How to
Repair
- Fail the job — terminal. Operator policy is "give up after this long".
- If the underlying scan should run again, schedule a fresh scan rather than reviving an expired job.
Gotchas
- Expired is the catch-all. If a job hits this, OTHER classes likely fired earlier; review the repair history.
- The 24h default is configured at JOB_TIMING_RULES.maxJobAgeMinutes — adjust per deploy.
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=fail |
Related
- Job Errors Overview — Category model