worksaudit okrequireMention and the bot's privacy mode. For the bot to see all group messages, you must disable privacy mode via /setprivacy with BotFather, or add the bot as a group administrator. Crucially, after making this change, you must remove and re-add the bot to the group for Telegram to apply the new settings. api.telegram.org. getMe returned 401 error, the token from BotFather is invalid or has expired. You'll need to update the botToken, tokenFile, or TELEGRAM_BOT_TOKEN for the default account. openclaw logs --follow. If the problem persists, the documentation suggests the root cause often circles back to proxy, DNS, or IPv6 misconfiguration. getUpdates 409 conflict, it means another OpenClaw gateway, script, or external poller is using the same bot token. OpenClaw's Telegram architecture is designed so that only one active long-polling instance should use a single bot token at a time. openclaw status --all, then openclaw doctor --fix, followed by openclaw gateway restart, and finally verifying with openclaw status --all again. plugin load failed: dependency tree corrupted, it means a channel is configured, but the plugin failed to load due to a corrupt dependency tree. The openclaw doctor --fix command is the one specified by the docs to clear old staging and authorization shadows before restarting the gateway. openclaw channels login telegram. Instead, it reads the token from your configuration or environment variables, requires channels.telegram.enabled: true, and then starts the gateway. openclaw pairing list telegram and approve the pairing, if necessary. worksaudit okrequireMention and the bot's privacy mode. For the bot to see all group messages, you must disable privacy mode via /setprivacy with BotFather, or add the bot as a group administrator. Crucially, after making this change, you must remove and re-add the bot to the group for Telegram to apply the new settings. api.telegram.org. getMe returned 401 error, the token from BotFather is invalid or has expired. You'll need to update the botToken, tokenFile, or TELEGRAM_BOT_TOKEN for the default account. openclaw logs --follow. If the problem persists, the documentation suggests the root cause often circles back to proxy, DNS, or IPv6 misconfiguration. getUpdates 409 conflict, it means another OpenClaw gateway, script, or external poller is using the same bot token. OpenClaw's Telegram architecture is designed so that only one active long-polling instance should use a single bot token at a time. openclaw status --all, then openclaw doctor --fix, followed by openclaw gateway restart, and finally verifying with openclaw status --all again. plugin load failed: dependency tree corrupted, it means a channel is configured, but the plugin failed to load due to a corrupt dependency tree. The openclaw doctor --fix command is the one specified by the docs to clear old staging and authorization shadows before restarting the gateway. openclaw channels login telegram. Instead, it reads the token from your configuration or environment variables, requires channels.telegram.enabled: true, and then starts the gateway. openclaw pairing list telegram and approve the pairing, if necessary.