{"version":"2.1.305","anchor":"http-409-is-now-treated-as-retryable","canonical_anchor":"http-409-is-now-treated-as-retryable","heading":"Requests that get a 409 conflict response are now retried","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/http-409-is-now-treated-as-retryable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Requests that get a 409 conflict response are now retried\n\nClaude Code now retries requests that get HTTP 409, as it already did for 408, 429 and server errors\n\n**What**\n\nWhen a request to a server fails, Claude Code decides from the response code whether to try again. It already retried on 408 (timeout), 429 (too many requests) and any 500-range server error. It now also retries on 409, which means the request conflicted with something else happening at the same time.\n\nSeparately, a 409 response is no longer read as meaning a request is already pending.\n\n**Why**\n\nConflict responses are now retried instead of failing straight away.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}