-
-
Notifications
You must be signed in to change notification settings - Fork 69.4k
[Bug]: Telegram polling consumes messages but never processes them — bot never responds (macOS, Apple Silicon) #22300
Description
Summary
Version: 2026.2.14 and 2026.2.19-2
OS: macOS, Mac Mini, Apple Silicon (arm64), Node 22.22.0
Description:
Telegram bot receives messages (double ticks show in Telegram app confirming delivery) but OpenClaw never processes them. lastInboundAt stays null indefinitely and the bot never replies.
Steps to reproduce
Fresh install of OpenClaw on macOS Apple Silicon
Configure Telegram bot token via openclaw config set
Set dmPolicy=open and allowFrom=["*"]
Start gateway — channel health shows running: true, probe ok: true, bot username confirmed correct
Send /start to bot from Telegram
Bot shows double ticks (delivered) in Telegram
curl getUpdates returns empty immediately — messages consumed by polling
lastInboundAt remains null in channel health
No inbound message appears in gateway log
No response from bot
Gateway log shows: Provider starts successfully, no crash errors logged, no inbound message events ever appear.
Additional notes:
Slack channel connects successfully (socket mode connected) but also silently drops inbound messages
Gemini API configured as model provider
Config confirmed correct via cat ~/.openclaw/openclaw.json
Expected behavior
Telegram bot receives messages (double ticks show in Telegram app confirming delivery) but OpenClaw never processes them. lastInboundAt stays null indefinitely and the bot never replies.
Actual behavior
Telegram bot receives messages (double ticks show in Telegram app confirming delivery) but OpenClaw never processes them. lastInboundAt stays null indefinitely and the bot never replies.
OpenClaw version
2026.2.14 and 2026.2.19-2
Operating system
macOS, Mac Mini, Apple Silicon (arm64), Node 22.22.0
Install method
nom
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response