{"version":"2.1.290","anchor":"trusted-device-error-text-reworded","canonical_anchor":"trusted-device-error-text-reworded","heading":"Clearer error when a session is tied to another device","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/trusted-device-error-text-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer error when a session is tied to another device\n\nThe error for a session bound to one device now says this machine could not prove it is that computer or a trusted device, and suggests \/login\n\n**What**\n\nSome sessions are bound to a single computer and accept messages only from it or from a trusted device. When a message is refused for that reason, the advice now reads: \"this machine could not prove it is the computer the session is bound to, or a trusted device; run \/login to enroll it\".\n\nIt still points you to `\/login` to sign in and add the machine.\n\n**Why**\n\nThe error now says what went wrong on your machine, not only the rule the session follows.\n\n- Area: Sessions\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}