{"version":"2.1.281","anchor":"cloud-sessions-bundle-chain-links-and-began-unbound-mess","canonical_anchor":"cloud-sessions-bundle-chain-links-and-began-unbound-mess","heading":"Cloud sessions: bundle chain links, and 'began unbound' messages","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-sessions-bundle-chain-links-and-began-unbound-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud sessions: bundle chain links, and 'began unbound' messages\n\nCloud sessions track bundle chains, and sessions started without a device binding now say so\n\n**Unclear.** The finding does not say what a bundle is or what the new fields do.\n\n**What**\n\nThe record of a cloud session's sync state gains `setAside`, `appliesLinks` and `need` fields, and bundles can now form a chain of links or stand alone.\n\nA cloud session started without being bound to a device now shows a message beginning 'This session began unbound (no sync-back or local commands):'.\n\n**Why**\n\nIf a cloud session starts unbound, you are told that its changes will not sync back and local commands will not run."}