{"version":"2.1.282","anchor":"new-telemetry-when-a-cancel-arrives-after-the-message-was-de","canonical_anchor":"new-telemetry-when-a-cancel-arrives-after-the-message-was-de","heading":"Cancelling an already-delivered remote message now reports the failure","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-telemetry-when-a-cancel-arrives-after-the-message-was-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cancelling an already-delivered remote message now reports the failure\n\nCancelling a message the remote client already delivered is no longer reported as a success, and the case is logged\n\n**What**\n\nIn the remote client that runs Claude Code without a screen, cancelling a queued message used to always report success. Now it reports whether the cancel actually worked, and logs an event when it failed because the message had already been delivered.\n\n**Why**\n\nA cancel that came too late no longer looks like it succeeded.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}