{"version":"2.1.225","anchor":"held-cross-session-messages-name-managed-or-repo-settings-as","canonical_anchor":"held-cross-session-messages-name-managed-or-repo-settings-as","heading":"Held cross-session messages name managed or repo settings as the cause","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-messages-name-managed-or-repo-settings-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Held cross-session messages name managed or repo settings as the cause\n\nWhen a peer message is held, you now see whether org or repo settings caused it.\n\n**What**\n\nWhen an inbound cross-session peer message is held, the explanation now tells you whether an org managed setting or the repository's own settings forced it, rather than just reporting an explicit setting.\n\n**Details**\n\n- Two new hold-reason cases: `managed-setting` and `repo-setting`, in addition to the plain `explicit-setting` case.\n- The repo case explains that a repo may only tighten, so your own \"accept\" cannot override it, and points at --setting-sources to exclude it.\n- The resolver was reworked to return both the effective value and which tier decided it; repo-level local and project settings are attributed as repoSettings.\n\n**Evidence**\n\n`This repository's settings set \"crossSessionInbound\" to \"hold\" (a repo may only tighten, so your own \"accept\" cannot override it); remove the repo setting or exclude it with --setting-sources.`, `This repository's settings set \"crossSessionInbound\" to \"hold\" (your own \"accept\" cannot override a repo tightening).`\n\n- Area: Cross-Session Messaging\n- Names: `--setting-sources`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}