{"version":"2.1.317","anchor":"http-529-overloaded-is-now-treated-like-a-retryable-429-er","canonical_anchor":"http-529-overloaded-is-now-treated-like-a-retryable-429-er","heading":"\"Overloaded\" API errors are now treated like rate-limit errors","tier":"notice","area":"API","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/http-529-overloaded-is-now-treated-like-a-retryable-429-er","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### \"Overloaded\" API errors are now treated like rate-limit errors\n\nClaude Code now treats the API's 529 \"overloaded\" error the same way it treats a 429 rate-limit error\n\n**Unclear.** It is not clear whether this means a 529 error is now retried automatically or handled some other way.\n\n**What**\n\nWhen Anthropic's API is too busy it answers with error 529, meaning overloaded. Claude Code now handles this error in the same way as error 429, which means too many requests.\n\n**Why**\n\nAn overloaded response can now be handled like a rate limit rather than as a plain failure.\n\n- Area: API\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}