{"version":"2.1.321","anchor":"stream-cut-retry-with-overloaded-specific-backoff-gated","canonical_anchor":"stream-cut-retry-with-overloaded-specific-backoff-gated","heading":"Interrupted replies can retry after a wait, with separate timing when overloaded","tier":"notice","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/stream-cut-retry-with-overloaded-specific-backoff-gated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Interrupted replies can retry after a wait, with separate timing when overloaded\n\nWhen a reply is cut off by a server error, Claude Code can wait before retrying; this is off unless switched on remotely\n\n**What**\n\nWhen a reply from the server is cut off partway by a server error, Claude Code can now work out how long to wait before trying again. When the error says the server is overloaded, the wait can follow:\n\n- `CLAUDE_CODE_OVERLOADED_RETRY_BASE_DELAY_MS`\n\n- `CLAUDE_CODE_OVERLOADED_RETRY_MAX_DELAY_MS`\n\nIf the wait cannot be set up, Claude Code retries with no wait. This whole behaviour is off unless it is switched on remotely.\n\n**Why**\n\nWhen it is switched on, a cut-off reply is retried after a pause rather than failing outright, which gives a busy server time to recover.\n\n- Flag `tengu_dreamy_flute`: Off in both readings (read for one account on one subscription tier against v2.1.321; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Network\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}