Gateway Down - config corruption after adding second telegram account

[arctic ferry]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[strong scarab]

Those errors are straight schema rules:

• channels.telegram.groupPolicy is group sender policy, and it only allows: "open" | "allowlist" | "disabled" (not "pairing").
• If you set DM policy to "open" (globally or for an account), schema forces an explicit opt‑in: allowFrom must include "*".

Fastest “get the gateway booting again” (no memory/session loss)

1. Edit your config file directly (JSON5): ~/.openclaw/openclaw.json
   Docs: https://docs.openclaw.ai/help/faq#what-format-is-the-config-where-is-it

2. Temporarily disable Telegram so the Gateway can start:

{
  channels: {
    telegram: { enabled: false },
  },
}