{"version":"2.1.247","anchor":"a-failed-inbound-support-lookup-counts-as-unreported","canonical_anchor":"a-failed-inbound-support-lookup-counts-as-unreported","heading":"A failed inbound-support lookup counts as unreported","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-failed-inbound-support-lookup-counts-as-unreported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A failed inbound-support lookup counts as unreported\n\nIf checking whether a peer session can receive messages fails, you get the unconfirmed-delivery caveat.\n\n**What**\n\nWhen the check for whether a peer session can receive cross-session messages fails outright, Claude Code logs the failure and treats that session as not having reported support, so the send carries the same unconfirmed-delivery caveat for the model and the shorter note on screen.\n\n**Details**\n\n- The log line is `[agents:cloud] warm inbound-report lookup failed`.\n- No gate: a lookup failure always falls back to the cautious wording rather than assuming delivery worked.\n\n**Evidence**\n\n`[agents:cloud] warm inbound-report lookup failed`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}