{"version":"2.1.280","anchor":"new-refusal-message-for-tool-calls-skipped-because-another-c","canonical_anchor":"new-refusal-message-for-tool-calls-skipped-because-another-c","heading":"New refusal message for tool calls skipped because another call in the same batch was denied","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-refusal-message-for-tool-calls-skipped-because-another-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New refusal message for tool calls skipped because another call in the same batch was denied\n\nClaude Code now shows a distinct message when a tool call is skipped because a check denied a different call in the same batch\n\n**What**\n\nWhen Claude Code sends several tool calls together as one batch, a permission check can deny one of them. Previously, the other calls in that batch that never got to run showed the same generic message used when a turn simply ended early. Now those skipped calls get their own message, explaining that the call was stopped because a check denied a sibling call in the same batch, that nothing about this call itself was refused, that it had no effect, and that it can be re-run if it's still needed.\n\n**Why**\n\nThis makes it clearer why a particular tool call didn't run: the call itself wasn't the problem, another call in the same batch was blocked and that stopped the rest from executing. Knowing that lets you distinguish a denied action from one that simply never got a chance to run, and tells you it's safe to retry.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}