{"version":"2.1.317","anchor":"tool-errors-after-an-interrupt-are-classified-as-interrupted","canonical_anchor":"tool-errors-after-an-interrupt-are-classified-as-interrupted","heading":"Some tool errors in unfinished turns now count as interrupted","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/tool-errors-after-an-interrupt-are-classified-as-interrupted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Some tool errors in unfinished turns now count as interrupted\n\nSome tool errors in a turn that did not finish are now marked interrupted instead of failed\n\n**Unclear.** It is not settled which errors are now marked as interrupted.\n\n**What**\n\nA tool call is one action Claude Code takes, such as running a command or editing a file. A turn is one round of Claude working on your request. When a tool call ends in an error and the turn did not finish, Claude Code now marks it as \"interrupted\" if the error matches a certain kind. Before, it was always marked \"failed\".\n\n**Why**\n\nThis changes how those tool calls are shown or reported after you stop a turn.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}