{"version":"2.1.225","anchor":"held-peer-messages-now-say-which-settings-tier-held-them","canonical_anchor":"held-peer-messages-now-say-which-settings-tier-held-them","heading":"Held peer messages now say which settings tier held them","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/held-peer-messages-now-say-which-settings-tier-held-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Held peer messages now say which settings tier held them\n\nWhen a cross-session message is held, you now see whether org, repo or local settings did it.\n\n**What**\n\nWhen an inbound cross-session message is held by an explicit setting, the notice names the settings layer responsible instead of giving a single generic cause.\n\n**Details**\n\n- the old single hold cause \"explicit-setting\" was replaced by source attribution, including `managed-setting`\n- policy settings render \"Your organization's managed settings set \\\"crossSessionInbound\\\" to \\\"hold\\\".\"\n- project and local settings render \"This repository's settings set \\\"crossSessionInbound\\\" to \\\"hold\\\" (your own \\\"accept\\\" cannot override a repo tightening).\"\n- a WeakMap holds the last-reported cause so a notice is re-emitted only when the cause changes\n\n**Evidence**\n\n`managed-setting`\n\n- Area: Cross-Session Messaging\n- Names: `crossSessionInbound`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}