{"version":"2.1.248","anchor":"clearer-error-when-a-remote-session-is-not-connected","canonical_anchor":"clearer-error-when-a-remote-session-is-not-connected","heading":"Clearer error when a remote session is not connected","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/clearer-error-when-a-remote-session-is-not-connected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Clearer error when a remote session is not connected\n\nRemote control requests now say plainly that the session is not connected.\n\n**What**\n\nControl requests sent from a remote session that has no manager now say the reason is that the session is not connected, on both the immediate path and the deferred permission-mode path.\n\n**Details**\n\n- The memoised sender's dependencies were corrected to track the remote-mode flag rather than a stale value.\n\n**Evidence**\n\n`[useRemoteSession] Cannot send control request (no manager): not connected`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}