{"version":"2.1.232","anchor":"cloud-sessions-state-plainly-that-they-cannot-message-other-","canonical_anchor":"cloud-sessions-state-plainly-that-they-cannot-message-other-","heading":"Cloud sessions state plainly that they cannot message other sessions","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-sessions-state-plainly-that-they-cannot-message-other-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud sessions state plainly that they cannot message other sessions\n\nCloud sessions now clearly refuse to deliver messages to other sessions instead of retrying.\n\n**What**\n\nA cloud session asked to deliver a message to another session now gets a refusal saying its credential is accepted for its own work but not for delivery elsewhere, and is told to say so rather than retry.\n\n**Details**\n\n- Looking up other sessions now distinguishes an empty list from an unreadable one: an unreadable local session list is logged and returns `{ sessions: [], unavailable: !0 }` instead of throwing.\n\n**Evidence**\n\n`this cloud session cannot message other sessions yet \\u2014 its credential is accepted for its own work but not for delivering to another session, so a reply from here is not possible; say so in your response instead of retrying`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}