{"version":"2.1.225","anchor":"held-peer-messages-record-their-hold-cause-on-re-evaluation","canonical_anchor":"held-peer-messages-record-their-hold-cause-on-re-evaluation","heading":"Held peer messages record their hold cause on re-evaluation","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/held-peer-messages-record-their-hold-cause-on-re-evaluation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Held peer messages record their hold cause on re-evaluation\n\nQueued messages from other sessions now report why they are still being held.\n\n**What**\n\nRe-running the inbound policy over queued cross-session messages now reports why each still-held message is held.\n\n**Details**\n\n- the hold cause, which may have changed since the message arrived, is passed to a listener along with the current queue depth\n- refused messages additionally fire a drop callback\n\n**Evidence**\n\n`[cross-session-inbound] dropped `\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}