{"version":"2.1.295","anchor":"artifact-create-retries-503-relay-responses-and-counts-retry","canonical_anchor":"artifact-create-retries-503-relay-responses-and-counts-retry","heading":"Creating an artifact retries more often when the server is busy","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-create-retries-503-relay-responses-and-counts-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Creating an artifact retries more often when the server is busy\n\nArtifact creation now keeps retrying when told to wait, and also retries some server-unavailable errors\n\n**What**\n\nWhen Claude Code creates an artifact and the server answers \"try again after a wait\", it now waits and retries several times, up to a limit, instead of only once. The handling of each response has changed:\n\n- Conflict (409) and too-many-requests (429) responses are still retried.\n\n- A service-unavailable (503) response is now retried too, but only when the request carries an idempotency key, a label that lets the server recognise a repeat of the same request, and the response matches a known message.\n\n- A 409 whose stated reason says an earlier attempt is still creating the artifact is now recognised, not only one marked that way in its headers.\n\nClaude Code also now counts how many retry waits happened.\n\n**Why**\n\nArtifact creation should fail less often when the service in between is under pressure, without creating the same artifact twice.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}