Errors and quotas
Read a run error in plain language and know the next action, without internal stack traces.
Before you start
- At least one run has been attempted.
Steps
Find the error
Overview and Usage show the last useful errors and the consumption.
Read the code
Provider codes are redacted and paired with a next action.
Resolve and retry
Reproduce with the test panel once the cause is fixed.
Expected result
Each failure is understood and reproducible; quota limits are visible before they are hit.
Errors and solutions
Key rejected
Rotate the key in the model connection; never paste the key into an unrelated field.
Quota reached
Raise the workspace limit or wait for the reset window; the error states which.
Provider unavailable
Retry later; the provider status is not presented as a user fault.
Screens
/usage — Usage: consumption, limits, last errors with next action.Reference of the console screen to capture (redacted) during the browser recipe (XP14). No fabricated image is shown.
Limits and dependencies
Standardised errors carry field/code/message/action; no internal stack is ever exposed to the client.
Provider documentation
—