{"version":"2.1.317","anchor":"retry-after-falls-back-to-a-parsed-error-body","canonical_anchor":"retry-after-falls-back-to-a-parsed-error-body","heading":"Rate-limit waits now work when the wait time is only in the error message","tier":"notice","area":"API","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/retry-after-falls-back-to-a-parsed-error-body","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Rate-limit waits now work when the wait time is only in the error message\n\nWhen an error has no Retry-After header, Claude Code now reads the wait time from the error itself before giving up on it\n\n**What**\n\nWhen a request is turned away for being sent too often, the reply can say how long to wait before trying again. This normally comes in a `retry-after` header (an extra detail attached to the reply). Claude Code used to read the wait time only from that header. When the header is missing, it now looks for the wait time in the error itself.\n\n**Why**\n\nSome proxies, which are go-between servers on the network, remove that header. Claude Code can now still wait the right amount of time before retrying, instead of guessing.\n\n- Area: API\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}