{"version":"2.1.246","anchor":"a-cloud-session-that-cannot-bind-to-this-machine-now-runs-cl","canonical_anchor":"a-cloud-session-that-cannot-bind-to-this-machine-now-runs-cl","heading":"A cloud session that cannot bind to this machine now runs cloud-only","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-cloud-session-that-cannot-bind-to-this-machine-now-runs-cl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A cloud session that cannot bind to this machine now runs cloud-only\n\nIf your machine can't be linked to a cloud session, it now runs cloud-only instead of failing.\n\n**What**\n\nIf the cloud service refuses to link the session to your machine, the session is kept and runs in the cloud instead of being archived and reported as a failure.\n\n**Details**\n\n- A warning notice explains the consequence: no commands, hooks or pulling files back will run on this machine, and that \"device binding is likely switched off there\".\n- Other unbound reasons still fail as before; only an explicit create refusal takes this path.\n\n**Evidence**\n\n`device binding is likely switched off there`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}