# spend_cap_raise_first

Resuming paused runs needs a higher cap first, because the month's spending is already at it.

## What happened

Resuming runs that were paused at the cap works only when one run's hold fits under it. When this month's spending is already at the cap, the resume is refused with 409 and the reply carries `cap` and `committed`.

## What to do

Raise the cap on the Compute page in the web app, then resume.

## Example

```json
{
  "error": {
    "code": "spend_cap_raise_first",
    "message": "This month's Forge spending is already at your cap. Raise the cap, then resume.",
    "detail": {
      "cap": 500,
      "committed": 500,
      "request_id": "3c6f9a52-8e1d-4b7a-9f20-6d41a8c5e7b3"
    }
  }
}
```