{"version":"2.1.232","anchor":"remote-control-disconnects-say-why","canonical_anchor":"remote-control-disconnects-say-why","heading":"Remote Control disconnects say why","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-disconnects-say-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control disconnects say why\n\nRemote Control disconnects now explain the cause, like another device taking over or the session being archived.\n\n**What**\n\nCode 4090 disconnects now carry a distinct reason each: a newer worker took over, the session is not active, the session was not found, or the client's view of the session is out of date. Each has plain-language text, for example that a session was ended or archived from another device or app.\n\n**Details**\n\n- The epoch-mismatch handler emits a session-not-active event alongside the existing stale and mismatch events, each now carrying a reason.\n- The diagnostic line was reformatted to `worker epoch mismatch (409) reason=...`.\n\n**Evidence**\n\n`this session was ended or archived from another device or app (code 4090)`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}