{"version":"2.1.225","anchor":"held-cross-session-peer-messages-supersede-re-arm-and-alread","canonical_anchor":"held-cross-session-peer-messages-supersede-re-arm-and-alread","heading":"Held cross-session peer messages: supersede, re-arm and already-resolved notice","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/held-cross-session-peer-messages-supersede-re-arm-and-alread","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Held cross-session peer messages: supersede, re-arm and already-resolved notice\n\nHeld peer messages now cancel their approval prompts cleanly instead of leaving stale ones hanging around.\n\n**What**\n\nThe inbound-hold hook keeps a per-message record with an abortable approval prompt, so held peer messages can be superseded, dropped or released cleanly instead of leaving orphaned prompts.\n\n**Details**\n\n- Superseded, dropped and released holds have their approval prompts cancelled via the stored abort handle.\n- When the approval surface returns, the expiry deadline is re-armed rather than being counted against the time with no surface available.\n- An approval or denial that lands after the message was already resolved by a mode or setting change posts a warning instead of acting.\n\n**Evidence**\n\n`That held message was already resolved before your `\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}