{"version":"2.1.293","anchor":"teleport-to-cloud-onmoved-and-error-rollback-handling","canonical_anchor":"teleport-to-cloud-onmoved-and-error-rollback-handling","heading":"Teleporting a session to the cloud now confirms the move and cleans up on failure","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/teleport-to-cloud-onmoved-and-error-rollback-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Teleporting a session to the cloud now confirms the move and cleans up on failure\n\nMoving a session to the cloud now reports when it has moved, asks to confirm, and cleans up if the request fails before sending\n\n**What**\n\nTeleporting moves a session you are running on your own machine so it continues in the cloud. That flow now:\n\n- reports when the session has moved, and when it may have moved;\n\n- asks you to confirm the move;\n\n- shows a message after the move.\n\nIf the request fails before it was sent, the session that was being set up is now cleaned up. Errors still begin with \"Couldn't teleport:\".\n\n**Why**\n\nHanding a session over to the cloud should be more reliable, and a failed attempt no longer leaves a half-set-up session behind.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}