> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# insufficient_credits

The account billed for a cloud run has insufficient usage. Check the funding source, add usage, or review auto-reload.

The `insufficient_credits` error means the balance that would pay for the run cannot cover it. Adding usage to a different account or to a personal allowance won’t fix a factory’s shared balance. The error code is the same whether the account uses dollars or credits.

Factory runs use [shared team or workspace funding](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/#funding-factory-runs), not a member’s included personal allowance. For standalone cloud runs, check the balance for the user or agent the run acts as. See [cloud run billing](https://docs.warp.dev/platform/team-access-billing-and-identity/#billing-for-cloud-agent-runs) for schedules, agent API key runs, and Enterprise terms.

* * *

## Details

-   **HTTP Status:** `403 Forbidden`
-   **Retryable:** No
-   **Task State:** FAILED

* * *

## When does this occur?

This error is returned when:

-   The billed user’s or team’s eligible balance is too low to start the run.
-   Auto-reload is off or cannot replenish the balance, such as when a purchase is blocked by the team’s limit.

See [Purchasing additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) for purchases, auto-reload, and spend limits.

* * *

## Example response

```json
{
  "type": "/factories/api-and-sdk/troubleshooting/errors/insufficient-credits/",
  "title": "The principal billed for this run has no remaining credits. Purchase add-on credits or raise the team-wide spend cap to continue.",
  "status": 403,
  "instance": "/api/v1/agent/tasks",
  "retryable": false
}
```

* * *

## How to resolve

### Factory runs

1.  In the [Warp Factories web app](https://platform.warp.dev), confirm the team that owns the factory. Open **Settings** > **Billing and usage** and check its shared team or workspace balance.
2.  [Add shared usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/#warp-factories), ask an admin to review auto-reload and the spend limit, or wait for the shared included allowance to reset. A personal allowance reset does not fund factory runs.
3.  Start the operation again after shared funding is available. The failed run is not retried automatically.

### Standalone cloud runs

1.  In the Warp app, open **Settings** > **Billing and usage** for the user or team billed for the run. Check [cloud run billing](https://docs.warp.dev/platform/team-access-billing-and-identity/#billing-for-cloud-agent-runs) if you aren’t sure which balance applies.
2.  [Purchase usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/#warp-terminal-and-local-agents), ask an admin to review auto-reload and the spend limit, or wait for the billed account’s applicable included allowance to reset.
3.  Start the operation again after funding is available.

* * *

## Related pages

-   **[Access, billing, and identity permissions](https://docs.warp.dev/platform/team-access-billing-and-identity/)** - Billing attribution for user-triggered and automated runs.
-   **[Purchasing additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/)** - Purchase usage and configure auto-reload.
-   **[Platform usage](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/)** - Agent-hour charges for cloud runs.
-   **[Cloud agents overview](https://docs.warp.dev/platform/)** - Billing and plan requirements for cloud agents.
