{"version":"2.1.290","anchor":"tasks-cancel-skipped-for-a-particular-abort-reason","canonical_anchor":"tasks-cancel-skipped-for-a-particular-abort-reason","heading":"Task cancel requests are skipped for one kind of abort","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/tasks-cancel-skipped-for-a-particular-abort-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Task cancel requests are skipped for one kind of abort\n\nClaude Code no longer sends a `tasks\/cancel` request when a task stops for one particular reason\n\n**Unclear.** Which stop reason skips the cancel is not known.\n\n**What**\n\nWhen a task is stopped, Claude Code used to always send a `tasks\/cancel` request. It now skips that request when the reason for stopping matches one specific value.\n\n**Why**\n\nIn practice, some stop flows no longer send a cancel.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}