{"version":"2.1.242","anchor":"dedicated-error-when-an-api-stream-sends-no-first-byte","canonical_anchor":"dedicated-error-when-an-api-stream-sends-no-first-byte","heading":"Dedicated error when an API stream sends no first byte","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/dedicated-error-when-an-api-stream-sends-no-first-byte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Dedicated error when an API stream sends no first byte\n\nA stream that never starts now gives a specific error with timings and a matchable code.\n\n**What**\n\nA stream that produces nothing within the first-byte window now raises a specific error rather than a generic timeout, and it carries the window length, how long was actually waited, and a stable error code you can match on.\n\n**Evidence**\n\n`\"No response from API within the first-byte window\"`\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}