Common Error Messages
Lookup table of user-facing errors with fixes.
Capacity and plan errors
| Message | What to do |
|---|---|
| Run allowance reached | Wait for the billing-period reset, upgrade, or add a run pack. New per-Run overage is not sold. |
| Active Monitor slots reached | Archive an unused Monitor, upgrade, or add a run pack. |
| Hosted generations would cost more than the plan allows | Reduce the sample or candidates, choose less expensive models, or use fully configured Enterprise provider keys. |
| Models not available on your plan | Choose models from an allowed candidate tier or upgrade. |
Traffic and evidence errors
| Message | What to do |
|---|---|
| No ingested corpus found | Connect a source or upload a file, then wait until received records appear. |
| Not enough replayable requests | Ingest enough structurally complete records to meet the requested sample and critical-category requirements. |
| Corpus must be reingested | Import the source again so readiness version 2 can record structural signals. |
| Observed control is not eligible | Fix the named response, model, system-prompt, retention, or sample gap, or explicitly choose replayed control. |
| Set workload.currentModelId | Select the exact catalog production model on the Monitor. A source model string is not enough. |
API errors
| Status | Meaning |
|---|---|
| 400 | Invalid JSON or request fields |
| 401 | Missing, invalid, expired, or revoked API key |
| 403 | Scope, role, plan, or model-tier restriction |
| 404 | The resource is absent from the authenticated workspace |
| 409 | Monitor capacity or resource state conflict |
| 422 | The request is shaped correctly but evidence or model validation failed |
| 429 | Rate limit, automation cap, or applicable legacy spending cap |