{"version":"2.1.295","anchor":"sse-transport-no-longer-drops-errors-after-abort","canonical_anchor":"sse-transport-no-longer-drops-errors-after-abort","heading":"Streaming connection errors are now logged after a disconnect","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/sse-transport-no-longer-drops-errors-after-abort","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Streaming connection errors are now logged after a disconnect\n\nErrors on one type of streaming connection are now logged and counted even after Claude Code has chosen to disconnect\n\n**What**\n\nSSE (server-sent events) is a kind of connection on which a server keeps streaming updates to Claude Code. Before, if Claude Code had already chosen to close such a connection and an error then arrived, the error was silently ignored. Those errors are now logged and counted like any other connection error, with the message \"SSETransport: Connection error:\".\n\n**Why**\n\nErrors on these connections are no longer hidden. One effect to watch for: connections Claude Code closes on purpose may now show up as connection errors in logs.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}