{"version":"2.1.247","anchor":"cancelling-while-a-background-agent-resumes-now-actually-can","canonical_anchor":"cancelling-while-a-background-agent-resumes-now-actually-can","heading":"Cancelling while a background agent resumes now actually cancels","tier":"notice","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cancelling-while-a-background-agent-resumes-now-actually-can","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cancelling while a background agent resumes now actually cancels\n\nCancelling while a background agent is resuming now stops it instead of reporting a read failure.\n\n**What**\n\nResuming a background agent reads its transcript; that read now receives the abort signal, re-checks it immediately afterwards, and raises the cancellation error. Previously an in-flight resume would run to completion and then be reported as a transcript read failure.\n\n**Details**\n\n- Abort errors are rethrown before the existing read-failure telemetry and transient-error classification, so cancellations no longer show up as failures.\n\n**Evidence**\n\n`subagent_resume_setup_read_failed`\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}