{"version":"2.1.296","anchor":"stopped-turn-error-log-now-reports-the-right-error","canonical_anchor":"stopped-turn-error-log-now-reports-the-right-error","heading":"Error log for a failed stopped-turn cleanup now shows the real error","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/stopped-turn-error-log-now-reports-the-right-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Error log for a failed stopped-turn cleanup now shows the real error\n\nWhen ending a stopped turn for a connected client fails, the log now records the error that actually happened\n\n**What**\n\nWhen Claude Code fails to end a stopped turn for the client it is talking to, it writes a log line starting \"ending the stopped turn for the client failed\". That line used to include an unrelated, older error. It now includes the error that actually caused the failure.\n\n**Why**\n\nThis is a small fix to diagnostics. Logs about this failure now point at the right problem.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}