{"version":"2.1.234","anchor":"sending-a-session-to-the-cloud-cancels-the-pending-resume-at","canonical_anchor":"sending-a-session-to-the-cloud-cancels-the-pending-resume-at","heading":"Sending a session to the cloud cancels the pending resume at the usage-limit reset","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/sending-a-session-to-the-cloud-cancels-the-pending-resume-at","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Sending a session to the cloud cancels the pending resume at the usage-limit reset\n\nHanding a session to the cloud now cancels a pending auto-resume at the usage-limit reset and tells you.\n\n**What**\n\nIf you hand a session off to the cloud while it is waiting to auto-continue after a usage limit resets, the pending resume is now cancelled and you are told, instead of a resume firing on a machine you have moved off.\n\n**Details**\n\n- A new cancellation reason `cloud_handoff` joins the existing background, desktop, relaunch and process-exit reasons.\n- The notice reads \"Automatic continue cancelled \u00b7 sending this session to the cloud, so the task will not resume here on its own when the usage limit resets (continue it in the cloud session)\", and is appended to the usage-limit error text.\n\n**Evidence**\n\n`Automatic continue cancelled \\xB7 sending this session to the cloud, so the task will not resume here on its own when the usage limit resets (continue it in the cloud session)`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}