{"version":"2.1.307","anchor":"out-of-credits-errors-without-an-http-status-are-treated-as","canonical_anchor":"out-of-credits-errors-without-an-http-status-are-treated-as","heading":"Out-of-credits errors are now recognised as a usage limit","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/out-of-credits-errors-without-an-http-status-are-treated-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Out-of-credits errors are now recognised as a usage limit\n\nSome out-of-credits errors that carry no HTTP status code are now recorded as a usage limit, not treated as a generic error\n\n**Unclear.** It is not clear exactly which errors and which accounts this new check applies to.\n\n**What**\n\nClaude Code reads your usage limits from the errors the server returns. Before, it only did this for errors with HTTP status code 429 (the code for \"too many requests\"). It now also handles some errors that have no status code, when they look like an out-of-credits error. In that case Claude Code records that extra usage beyond your plan is refused, with the reason `out_of_credits`.\n\n**Why**\n\nIf you run out of credits, Claude Code should now track that as your usage state rather than treating it as an unexplained failure.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}