{"version":"2.1.286","anchor":"stream-retry-backoff-now-bounded-by-remaining-deadline","canonical_anchor":"stream-retry-backoff-now-bounded-by-remaining-deadline","heading":"Retries of a failed response stream now fit inside the time left","tier":"notice","area":"API Requests","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/stream-retry-backoff-now-bounded-by-remaining-deadline","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Retries of a failed response stream now fit inside the time left\n\nWhen a response stream fails, the wait before retrying is now capped to the time remaining, and stalled requests are retried more readily\n\n**Unclear.** The length of the deadline, the minimum time left, and one further condition on retrying are not known.\n\n**What**\n\nWhen a response from the model fails partway, Claude Code waits a short time and tries again. That wait is now shortened so it never runs past the deadline for the request.\n\nClaude Code now retries in either of these cases:\n\n- The request stalled before the server sent anything back.\n\n- At least a minimum amount of time is still left before the deadline.\n\nBefore, it retried only when the full wait fitted inside the deadline.\n\n**Why**\n\nA request that stalls before any reply arrives is now retried more persistently instead of being given up on because the full wait would not fit.\n\n- Area: API Requests\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}