{"version":"2.1.318","anchor":"stopped-api-error-messages-excluded-from-in-progress-check","canonical_anchor":"stopped-api-error-messages-excluded-from-in-progress-check","heading":"API error messages are no longer treated as replies still in progress","tier":"notice","area":"API Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/stopped-api-error-messages-excluded-from-in-progress-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### API error messages are no longer treated as replies still in progress\n\nAn error shown in place of Claude's reply is no longer counted as an unfinished turn or one waiting on a tool\n\n**What**\n\nWhen a request to Anthropic's servers fails, Claude Code shows an error message where Claude's reply would be. Claude Code no longer treats that error message as an unfinished reply. It also no longer treats it as a reply that is waiting for a tool to finish or that has no stop reason.\n\n**Why**\n\nThis likely stops a failed request from being handled as though Claude were still replying.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}