{"version":"2.1.242","anchor":"cloud-sessions-report-queued-commands-dropped-by-an-interrup","canonical_anchor":"cloud-sessions-report-queued-commands-dropped-by-an-interrup","heading":"Cloud sessions report queued commands dropped by an interrupt","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-sessions-report-queued-commands-dropped-by-an-interrup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud sessions report queued commands dropped by an interrupt\n\nHeadless cloud clients now see a cancelled status for each queued command an interrupt dropped.\n\n**What**\n\nA tool driving a cloud session through the headless `--cloud` client now gets a 'cancelled' status, and only that status, for each queued command an interrupt with `cancel_queued:true` dropped, so it can tell that those commands will never run.\n\n**Details**\n\n- The cancellation messages follow the interrupt's own success response and are not ordered against the result of the turn that was interrupted.\n- Identifiers you do not recognise may appear, because another client connected to the same session may have queued the prompt.\n- Documented for the stdout stream in `-p` and SDK sessions, headless `--cloud` client only.\n\n**Evidence**\n\n`A host driving a cloud-hosted session through the headless `--cloud` client also receives 'cancelled' (and only that state) after its interrupt with cancel_queued:true`\n\n- Area: Cloud Sessions\n- Names: `--cloud`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}