OpenClaw Telegram Provider Initialization Hang (2026.2.24+)
Summary
Telegram provider gets stuck during initialization and never starts polling for messages. This affects both2026.2.24 and 2026.2.25, and persists even when downgrading to 2026.2.23 on this specific system.
## Environment
- OpenClaw Version: 2026.2.24 / 2026.2.25 (reproduced on both, doesn't fix on 2.23 for this user)
- Node.js: v22.22.0
- OS: Linux 6.8.0-101-generic
- Two different Telegram bot tokens tested
- Multiple group types tested (forum with topics, flat groups)
## Symptoms
1. Provider starts but hangs: Logs show
[default] starting providerinitialization never completes
2. No error message:
lastErrornull3. Status shows not running:
openclaw gateway call healthrunning: false4. Messages consumed but not routed: Telegram offset advances (messages arrive), but they don't route to
agents
5. Provider never reaches polling loop: Hangs after network configuration, before polling begins
## Reproduction Steps
1. Install OpenClaw 2026.2.24 or 2026.2.25
2. Configure Telegram channel with valid bot token
3. Add bot to group(s)
4. Run
systemctl --user restart openclaw-gateway.service5. Check
openclaw gateway call healthrunning: false6. Send message to group → No response, but offset advances
## Log Excerpt
## Workaround
Unknown. Downgrading to 2026.2.23 fixes the issue for some users but not others.
## Related
Discord reports indicate multiple users experiencing this issue with 2026.2.24+.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
