{"version":"2.1.301","anchor":"retry-after-delay-no-longer-capped","canonical_anchor":"retry-after-delay-no-longer-capped","heading":"Server-requested retry waits are no longer capped","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/retry-after-delay-no-longer-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Server-requested retry waits are no longer capped\n\nWhen a server says how long to wait before retrying, Claude Code now uses that full wait instead of cutting it down to a maximum\n\n**Unclear.** It is not clear whether some other limit still shortens very long waits.\n\n**What**\n\nA server can include a number in its response that tells Claude Code how long to wait before trying the request again. Claude Code used to cut that number down to a fixed maximum. It now uses the server's number as given, as long as it is greater than zero.\n\n**Why**\n\nClaude Code now follows the server's timing more closely. A very large value from a server can also make Claude Code wait a long time before it retries.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}