{"version":"2.1.302","anchor":"tool-calls-can-be-abandoned-tool-use-error-carries-toolusei","canonical_anchor":"tool-calls-can-be-abandoned-tool-use-error-carries-toolusei","heading":"Tool calls are skipped once they have been abandoned","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/tool-calls-can-be-abandoned-tool-use-error-carries-toolusei","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Tool calls are skipped once they have been abandoned\n\nClaude Code skips a tool call that has been marked as abandoned, so it no longer runs after the request for it was given up\n\n**Unclear.** It is not stated what marks a tool call as abandoned, so it is unclear which situations, such as pressing interrupt, now skip calls.\n\n**What**\n\nA tool call is a single action Claude takes, such as reading a file or running a command. Before each call runs, Claude Code now checks whether the call has been abandoned. If it has, the call is skipped.\n\nWhen a tool call is rejected before running, the error report now also carries the ID of that call.\n\n**Why**\n\nAn action no longer runs after whatever asked for it has stopped waiting for the result.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}