{"version":"2.1.290","anchor":"channels-held-off-when-the-egress-policy-fails-to-load","canonical_anchor":"channels-held-off-when-the-egress-policy-fails-to-load","heading":"Channels wait for your organisation's policy and say so","tier":"notice","area":"Channels","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/channels-held-off-when-the-egress-policy-fails-to-load","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Channels wait for your organisation's policy and say so\n\nChannels now stay off until your organisation's policy loads, and the startup banner explains that messages are dropped meanwhile\n\n**What**\n\nChannels lets outside services send messages into a Claude Code session. Channels now waits for your organisation's policy before it delivers anything.\n\n- The status text listing what stays off until the network policy loads now names Channels alongside web fetch and design sync.\n\n- The Channels startup banner has a new state while the policy is still loading. It says Channels is \"waiting for your organization's policy\" and that \"Messages are dropped until it loads\".\n\n- If the policy cannot be reached because the network does not provide it, the banner says \"This network does not serve it, so messages are dropped this session\".\n\n- Incoming channel messages are dropped until the policy is settled. Before, the banner only had the policy-blocked, disabled and third-party states.\n\n**Why**\n\nIf your organisation's policy cannot be loaded, Channels stays off instead of letting messages through unchecked. Messages that arrive in the meantime are lost, and the banner now tells you why instead of leaving them to vanish silently.\n\n- Area: Channels\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}