HEART ai.budget-exceeded H-07004
AI budget used up. The AI budget is used up. AI calls are stopped.
| Code | HEART ai.budget-exceeded; inside a message "code": "ai.budget-exceeded" |
|---|---|
| H-number | H-07004: area 07, code 004 |
| Area | ai: AI providers, models, budgets |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Products that use an AI model |
Likely causes
- Normal use has spent the budget for the period.
- A cost spike or a loop used it up early.
- The budget was set lower than real use needs.
How to fix or prevent it
- Find and fix any loop or spike first.
- Raise the budget if the use was worth it, or wait for the next period.
- Check that the product still does its job without the model, as a HEART must.
What the HEART does by itself
It stops calling the model, and goes on with local thinking or rules only. It never spends past the budget. It resolves when the next period starts or the budget is raised.
When to call service
Not needed, unless the product does not work without the model, which a HEART must.
Related codes
ai.budget-near-limitH-07003: AI budget near its limitai.cost-spikeH-07002: AI cost spikeai.provider-unavailableH-07001: AI provider unavailable
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)