Rate Limit Exhausted
The slowest-wins rate resolution across the job's scanner, subnet, and port-list levels evaluates to 0 probes/sec. Operator policy prevents any throughput.
How to
Diagnose
- Identify which level (scanner / subnet / port-list) has the 0-rate config
- Check Config > Subnets and Config > Port Lists for the affected entries
Fix
- Set a non-zero rate at the appropriate level
- Redispatch the affected jobs (they will pick up the new rate at next claim)
Gotchas
- In v1 this detector is a STUB — it never fires. Once the live re-resolution wiring lands, this class will activate.
- A 0-rate at the scanner level means "no probing from this scanner ever"; check that this is intentional.
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=redispatch | fail |
Related
- Job Errors Overview — Category model
- Subnets — Subnet-level rate config
- Port Lists — Port-list-level rate config