{"version":"2.1.321","anchor":"mid-stream-tls-errors-are-treated-as-truncated-streams","canonical_anchor":"mid-stream-tls-errors-are-treated-as-truncated-streams","heading":"A secure-connection error partway through a reply is handled as a cut-off reply","tier":"notice","area":"Streaming","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mid-stream-tls-errors-are-treated-as-truncated-streams","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### A secure-connection error partway through a reply is handled as a cut-off reply\n\nIf a secure-connection error hits after a reply has started arriving, Claude Code now treats it the same as a reply that was cut short\n\n**Unclear.** Whether a reply cut off this way is now retried automatically is not known.\n\n**What**\n\nThe model's reply arrives in pieces, as a stream. If the secure (TLS) connection fails after at least one piece has arrived, Claude Code now logs the error and treats it as a stream that was cut short. Its usual handling for cut-off replies then applies.\n\n**Why**\n\nA connection reset in the middle of a reply is now handled the same way as any other interrupted reply, instead of as a separate kind of failure.\n\n- Area: Streaming\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}