{"version":"2.1.234","anchor":"messaging-a-peer-a-cloud-session-cannot-reach-is-refused-bef","canonical_anchor":"messaging-a-peer-a-cloud-session-cannot-reach-is-refused-bef","heading":"Messaging a peer a cloud session cannot reach is refused before delivery","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/messaging-a-peer-a-cloud-session-cannot-reach-is-refused-bef","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Messaging a peer a cloud session cannot reach is refused before delivery\n\nCloud sessions refuse up front to message peers that require a trusted device, with an explanation.\n\n**What**\n\nSending to a peer that requires a trusted device from a cloud session is now refused up front with an explanation instead of being attempted and failing.\n\n**Details**\n\n- Resolution of a `bridge:` target checks a cached \"unreachable from here\" marker and returns a refusal with reason `unreachable_elevated`.\n- The message says the target is \"not reachable from a cloud session \u2014 that session requires a trusted device, which a cloud session never has; message it from one of your own machines instead\".\n\n**Evidence**\n\n`not reachable from a cloud session \\u2014 that session requires a trusted device, which a cloud session never has; message it from one of your own machines instead`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}