{"version":"2.1.247","anchor":"failed-streaming-connections-are-drained-before-being-classi","canonical_anchor":"failed-streaming-connections-are-drained-before-being-classi","heading":"Failed streaming connections are drained before being classified","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/failed-streaming-connections-are-drained-before-being-classi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Failed streaming connections are drained before being classified\n\nFailed streaming responses are drained and re-checked for cancellation before being labelled an error.\n\n**What**\n\nWhen a streaming connection returns a non-ok response, the client now reads and discards the body with a timeout and re-checks whether the request was already cancelled before deciding what kind of failure it was, instead of tearing the stream down immediately.\n\n**Details**\n\n- The event envelope now parses only the event type; the optional withheld payload field was removed.\n- One entry was dropped from the set of recognised notification event types.\n\n**Evidence**\n\n`cli_sse_connect_http_error`\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}