{"version":"2.1.261","anchor":"escalated-retry-windows-for-the-first-byte-stream-timeout","canonical_anchor":"escalated-retry-windows-for-the-first-byte-stream-timeout","heading":"Escalated retry windows for the first-byte stream timeout","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/escalated-retry-windows-for-the-first-byte-stream-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Escalated retry windows for the first-byte stream timeout\n\nRetrying a stalled API request now waits longer on the retry than on the first attempt.\n\nThe first-byte stream timeout logic, which aborts an API request if no response headers arrive in time, now tracks per-request retry state via `streamFirstByteArmedRequestIds`. On a retry of the same request it computes an escalated (larger) retry window instead of reusing the original first-attempt window. The request timeout\/retry budget calculator now returns an object with `escalated`, `firstWindowMs`, and `retryWindowMs` instead of a single number, and these values are surfaced in a new `noResponse` field on the shaped API error, reporting how long the client waited before giving up.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}