{"version":"2.1.299","anchor":"stall-retry-no-longer-requires-before-headers","canonical_anchor":"stall-retry-no-longer-requires-before-headers","heading":"Stalled replies can be retried even after the reply has started","tier":"soon","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/stall-retry-no-longer-requires-before-headers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Stalled replies can be retried even after the reply has started\n\nA reply that stalls can now be retried even if the stall happens after the response has begun, when an enabling switch is on\n\n**Unclear.** It is not clear what the enabling condition is, or whether it is a remotely controlled switch that may be off.\n\n**What**\n\nClaude Code streams the model's reply as it arrives. Before, it only retried a stalled reply if the stall happened before the server had sent its first response details. Now a stall is eligible for retry whenever it happens, as long as a separate enabling condition is met.\n\n**Why**\n\nReplies that freeze partway through may now be retried automatically instead of failing.\n\n- Area: API Requests\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}