Telegram DM messages received but never dispatched to agent
Environment:
OpenClaw version: 2026.2.15
OS: Ubuntu Linux 6.8.0-100-generic (x64)
Node: v22.22.0
Telegram bot: @Sock_Claw_Bot (polling mode)
Config (relevant parts):
{
"channels": {
"telegram": {
"enabled": true,
"dmPolicy": "allowlist",
"allowFrom": ["5244466859"],
"groupPolicy": "allowlist",
"streamMode": "partial",
"network": { "autoSelectFamily": true }
}
}
}
Problem:
openclaw status shows Telegram as ON/OK
openclaw channels status --probe shows "works"
Bot can send messages to users (outbound works)
Bot receives inbound DMs (visible in logs as telegram update: {...})
Messages are never dispatched to the agent (no "message queued" or "session state" logs)
No errors or policy rejection logs
Logs showing the issue:
// Message received:
telegram update: {"update_id":238125668,"message":{"message_id":49,"from":{"id":5244466859,...},"chat":{"id":5244466859,"type":"private"},"text":"hey there"}}
// No subsequent dispatch/queue logs - message silently dropped
What I've tried:
dmPolicy: "open" with allowFrom: ["", "5244466859"]
dmPolicy: "allowlist" with allowFrom: ["5244466859"]
dmPolicy: "pairing" (no pending pairing requests)
Multiple gateway restarts (clean stop/start)
Killed all processes to eliminate conflict errors
Verified no webhook blocking (getWebhookInfo shows empty URL)
Enabled full diagnostics (flags: [""])
Ran openclaw doctor --fix
Routing log (shows peer=none at startup):
[routing] resolveAgentRoute: channel=telegram accountId=default peer=none guildId=none teamId=none bindings=0
Expected: Telegram DMs should be queued and processed by the agent like webchat messages.
Actual: Messages received but silently dropped between raw-update and dispatch.
OpenClaw version: 2026.2.15
OS: Ubuntu Linux 6.8.0-100-generic (x64)
Node: v22.22.0
Telegram bot: @Sock_Claw_Bot (polling mode)
Config (relevant parts):
{
"channels": {
"telegram": {
"enabled": true,
"dmPolicy": "allowlist",
"allowFrom": ["5244466859"],
"groupPolicy": "allowlist",
"streamMode": "partial",
"network": { "autoSelectFamily": true }
}
}
}
Problem:
openclaw status shows Telegram as ON/OK
openclaw channels status --probe shows "works"
Bot can send messages to users (outbound works)
Bot receives inbound DMs (visible in logs as telegram update: {...})
Messages are never dispatched to the agent (no "message queued" or "session state" logs)
No errors or policy rejection logs
Logs showing the issue:
// Message received:
telegram update: {"update_id":238125668,"message":{"message_id":49,"from":{"id":5244466859,...},"chat":{"id":5244466859,"type":"private"},"text":"hey there"}}
// No subsequent dispatch/queue logs - message silently dropped
What I've tried:
dmPolicy: "open" with allowFrom: ["", "5244466859"]
dmPolicy: "allowlist" with allowFrom: ["5244466859"]
dmPolicy: "pairing" (no pending pairing requests)
Multiple gateway restarts (clean stop/start)
Killed all processes to eliminate conflict errors
Verified no webhook blocking (getWebhookInfo shows empty URL)
Enabled full diagnostics (flags: [""])
Ran openclaw doctor --fix
Routing log (shows peer=none at startup):
[routing] resolveAgentRoute: channel=telegram accountId=default peer=none guildId=none teamId=none bindings=0
Expected: Telegram DMs should be queued and processed by the agent like webchat messages.
Actual: Messages received but silently dropped between raw-update and dispatch.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
