{"version":"2.1.219","anchor":"interrupt-no-longer-double-reports-cancelled-queued-commands","canonical_anchor":"interrupt-no-longer-double-reports-cancelled-queued-commands","heading":"Interrupt no longer double-reports cancelled queued commands","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/interrupt-no-longer-double-reports-cancelled-queued-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Interrupt no longer double-reports cancelled queued commands\n\nInterrupting queued commands no longer reports the same cancellation twice or lists it as still queued.\n\n**What**\n\nInterrupting a session with queued commands emitted a second \"cancelled\" lifecycle callback for commands whose cancel had already been acknowledged, and listed them again as still queued.\n\n**Details**\n\n- The command queue gains `consumeCancelPendingAcked` \/ `hasCancelPendingAcked` on top of the existing cancel-pending set\n- Drain suppresses a second `\"cancelled\"` lifecycle callback for a uuid whose cancel was already acknowledged\n- The interrupt control_response filters those uuids out of `still_queued`\n- Affects SDK clients watching command lifecycle around `cancel_queued`\n\n**Evidence**\n\n`consumeCancelPendingAcked`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}