{"version":"2.1.317","anchor":"overloaded-turned-away-responses-now-retry-or-fail-fast-de","canonical_anchor":"overloaded-turned-away-responses-now-retry-or-fail-fast-de","heading":"Overload rejections fail fast in background sessions and retry in persistent ones","tier":"notice","area":"API","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/overloaded-turned-away-responses-now-retry-or-fail-fast-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Overload rejections fail fast in background sessions and retry in persistent ones\n\nWhen the service turns a request away because it is overloaded, background sessions now stop at once and persistent sessions retry\n\n**Unclear.** It is not stated when a response counts as turned away for overload, or whether this behaviour applies to everyone.\n\n**What**\n\nA session is one running conversation with Claude Code. Sometimes Claude Code gets no response because the service turned the request away as overloaded. What happens next now depends on the kind of session:\n\n- Background sessions fail straight away.\n\n- Persistent sessions retry.\n\nAll other cases of no response go through the same reconnect check as before, then the usual waiting and retrying.\n\n**Why**\n\nWhen the service is overloaded, a background session now ends quickly, while a persistent session keeps trying.\n\n- Area: API\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}