{"version":"2.1.295","anchor":"hedged-request-retries-when-first-answer-is-not-acceptable","canonical_anchor":"hedged-request-retries-when-first-answer-is-not-acceptable","heading":"Backup requests keep the first usable fallback result","tier":"notice","area":"API Retries","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/hedged-request-retries-when-first-answer-is-not-acceptable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Backup requests keep the first usable fallback result\n\nWhen Claude Code sends a backup request, an unacceptable result is now held as a fallback while another attempt runs\n\n**What**\n\nFor some requests, Claude Code sends a backup copy if the first is slow and uses whichever answers. If one attempt now comes back successfully but does not pass the check for a proper answer while another attempt is still running, Claude Code keeps that result as a fallback. A later attempt that also fails the check no longer replaces it. This is on by default.\n\n**Why**\n\nThis can change which response is used when a delayed backup request races the original.\n\n- Area: API Retries\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}