{"version":"2.1.219","anchor":"queued-command-cancellations-are-acknowledged-once","canonical_anchor":"queued-command-cancellations-are-acknowledged-once","heading":"Queued-command cancellations are acknowledged once","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/queued-command-cancellations-are-acknowledged-once","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Queued-command cancellations are acknowledged once\n\nCancelled queued commands are reported once and no longer linger in the interrupt receipt.\n\n**What**\n\nA queued command whose cancellation was already reported no longer produces a second cancelled event, and no longer appears as still queued in the interrupt receipt.\n\n**Details**\n\n- the command queue gained `consumeCancelPendingAcked` and `hasCancelPendingAcked` on top of the existing cancel-pending marks\n- commands whose \"cancelled\" lifecycle event was already emitted are skipped on later passes\n- those commands are filtered out of the `still_queued` list in the interrupt receipt sent to SDK clients\n\n**Evidence**\n\n`still_queued`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}