spend_cap_reached

What happened#

You can set a cap on what Forge spends in a month. A run that needs more room than is left under it, or any run while hosted runs are paused at the cap, is refused with 409. The reply carries reason, cap, committed and room. A run that was already queued can also end with this code when the machine that claims it finds no room left.

What to do#

Raise the cap or resume runs on the Compute page in the web app, then start the run again.

Example#

{
  "error": {
    "code": "spend_cap_reached",
    "message": "This run does not fit under your monthly spending cap. Raise the cap or resume runs on the Compute page.",
    "detail": {
      "reason": "cap_reached",
      "cap": 500,
      "committed": 500,
      "room": 0,
      "request_id": "3c6f9a52-8e1d-4b7a-9f20-6d41a8c5e7b3"
    }
  }
}