{"version":"2.1.232","anchor":"remote-session-close-reasons-are-classified-in-one-table","canonical_anchor":"remote-session-close-reasons-are-classified-in-one-table","heading":"Remote session close reasons are classified in one table","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-session-close-reasons-are-classified-in-one-table","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote session close reasons are classified in one table\n\nA session taken over on another device is now reported as such instead of a generic disconnect.\n\n**What**\n\nClose codes from the remote session connection now map to named outcomes in a shared table, so a session that was taken over elsewhere is reported as ended elsewhere rather than as a generic transport close.\n\n**Details**\n\n- Taken over by a worker maps to superseded; an inactive session maps to archived; epoch conflicts, missing causes, 403 and 404 map to an unknown supersession.\n\n**Evidence**\n\n`session_not_active`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}