{"version":"2.1.225","anchor":"send-message-clearer-story-about-sessions-on-other-machines","canonical_anchor":"send-message-clearer-story-about-sessions-on-other-machines","heading":"send_message: clearer story about sessions on other machines","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/send-message-clearer-story-about-sessions-on-other-machines","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### send_message: clearer story about sessions on other machines\n\nMessaging an unknown peer now explains that sessions on other machines could not be checked, so retry.\n\n**What**\n\nThe old \"reply-only bridge session\" refusal was removed, and unresolved peer names now explain that Remote Control sessions on other machines could not be checked, with a suggestion to retry.\n\n**Details**\n\n- Unresolved names no longer fall back to the send_message connector.\n- Timeouts are now reported as `\"timeout\"` instead of `not_reachable`.\n- The isolatePeerMachines prompt is assembled from whichever of the cloud or bridge lookups actually failed.\n\n**Evidence**\n\n`sessions on other machines could not be checked just now, so they were not searched.`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}