# Generation and billing statuses

> Map execution and billing states to safe polling, completion, retry, and review behavior.

Canonical: https://entirefeed.com/docs/reference/statuses

Execution status and billing status are related but distinct. Always inspect both before deciding that work is complete or balance is available again.

## Generation status

| Status | Phase | Required action |
| --- | --- | --- |
| `queued` | Active | Keep polling. Cancellation can be requested. |
| `running` | Active | Keep polling. Cancellation is best effort. |
| `succeeded` | Terminal | Read ordered output assets, structured data, and final usage. |
| `failed` | Terminal | Inspect error and usage. Retry only after classifying the failure. |
| `cancelled` | Terminal | Inspect final usage. The latest cancelled attempt may be retried. |
| `manual_review` | Terminal for automation | Stop automated actions until status and billing are resolved. |

## Billing status

| Status | Meaning | Balance behavior |
| --- | --- | --- |
| `reserved` | The current estimate is held while work is active. | Included in reserved balance, not available balance. |
| `settled` | Final usage was charged. | The settled amount remains spent; unused hold can be released. |
| `released` | The held amount was returned. | Released funds are available again. |
| `manual_review` | Final cost could not be resolved automatically. | The hold remains unavailable until resolution. |