{"version":"2.1.228","anchor":"device-binding-failures-explain-themselves","canonical_anchor":"device-binding-failures-explain-themselves","heading":"Device-binding failures explain themselves","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/device-binding-failures-explain-themselves","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Device-binding failures explain themselves\n\nIf a session can't be tied to this machine, the error now says which situation happened.\n\n**What**\n\nWhen a session cannot be tied to this machine, the error now says which of four situations occurred rather than showing a bare code.\n\n**Details**\n\n- Covered cases: the session could not be read, the session is bound to another device, this machine has no device registration, and the local registration could not be read.\n- The new reasons merge into the existing device-binding message map.\n\n**Evidence**\n\n`this session is bound to another device (a different machine or config directory)`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}