{"version":"2.1.282","anchor":"side-query-503s-without-a-dispatch-header-now-retried-once","canonical_anchor":"side-query-503s-without-a-dispatch-header-now-retried-once","heading":"More background requests are retried after a temporary server error","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/side-query-503s-without-a-dispatch-header-now-retried-once","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### More background requests are retried after a temporary server error\n\nBackground requests that get a 503 server error are now retried once in more cases, usually after a short wait\n\n**Unclear.** How long the wait before the retry lasts is not known.\n\n**What**\n\nBesides the main conversation, Claude Code sends smaller background requests to the API. A 503 error means the server is temporarily unable to handle a request. Before, only one kind of 503 reply to these background requests was retried. Now any 503 that comes back without a particular header is retried once:\n\n- a reply that says not to retry is still retried once without waiting\n\n- any other 503 is retried once after a short wait\n\n**Why**\n\nFewer background requests should fail when the API has a brief hiccup.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}