{"version":"2.1.224","anchor":"peer-lookups-say-when-other-machines-sessions-could-not-be-c","canonical_anchor":"peer-lookups-say-when-other-machines-sessions-could-not-be-c","heading":"Peer lookups say when other machines' sessions could not be checked","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/peer-lookups-say-when-other-machines-sessions-could-not-be-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Peer lookups say when other machines' sessions could not be checked\n\nIf peer listing failed, the not-found message now says other machines could not be checked.\n\n**What**\n\nWhen you name a peer session that is not found, the refusal now adds a note if the listing of sessions reachable over the remote bridge timed out or failed, explaining those sessions can only be replied to from this machine and cannot be addressed by name.\n\n**Details**\n\n- Backed by a marker recording why the listing failed, with values `timeout` and `fetch_failed`.\n\n**Evidence**\n\n`and files can't be sent to it by name from this machine.`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}