{"version":"2.1.239","anchor":"device-pairing-reports-hitting-a-session-limit-distinctly","canonical_anchor":"device-pairing-reports-hitting-a-session-limit-distinctly","heading":"Device pairing reports hitting a session limit distinctly","tier":"notice","area":"Device Pairing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/device-pairing-reports-hitting-a-session-limit-distinctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Device pairing reports hitting a session limit distinctly\n\nDevice pairing now names a per-account session cap instead of failing generically.\n\n**What**\n\nPairing a device can now fail with `device_session_limit`, a named error for hitting a per-account device or session cap, rather than a generic failure.\n\n**Details**\n\n- Added to both the device-registration error list and the check for which device errors are recognised and worth naming to the user, alongside `duplicate_device_id` and `device_name_in_use`.\n\n**Evidence**\n\n`device_session_limit`\n\n- Area: Device Pairing\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}