Telegram group messages not received after upgrade to 2026.2.24+
Resolved 💬 2 comments Opened Feb 28, 2026 by eNNNo Closed Feb 28, 2026
Description
After upgrading from 2026.2.23 to 2026.2.26, Telegram bots stopped receiving group messages. DMs continued to work fine, and the bot could still send messages to groups, but incoming group messages were not being received/processed.
Environment
- OpenClaw version (broken): 2026.2.24, 2026.2.25, 2026.2.26
- OpenClaw version (working): 2026.2.23
- OS: macOS (Darwin 25.3.0 arm64)
- Node: v25.6.0
Steps to Reproduce
- Configure a Telegram bot with group support (multi-account setup with
familyaccount) - Add bot to a group with
requireMention: false - Disable privacy mode in BotFather (
/setprivacy→ Disable) - Make bot admin in the group
- Upgrade to 2026.2.26
- Send a message in the group
Expected: Bot receives and processes the group message
Actual: No response, no logs showing message received
Verification
getMeAPI showscan_read_all_group_messages: true(privacy mode off)getChatMemberconfirms bot is admingetWebhookInfoshows no webhook conflict- Bot can successfully send messages to the group via
messagetool - DMs to the same bot work fine
- Gateway status shows
worksfor the Telegram account
Config (redacted)
{
"channels": {
"telegram": {
"enabled": true,
"accounts": {
"family": {
"enabled": true,
"groups": {
"-1003703340043": { "requireMention": false }
},
"groupPolicy": "allowlist"
}
}
}
}
}
Workaround
Downgrade to 2026.2.23:
npm install -g openclaw@2026.2.23
openclaw gateway restart
Notes
- The group migrated from a regular group to supergroup during debugging (ID changed from
-4995470723to-1003703340043), but this was not the root cause - OpenClaw auto-detected the migration and logged it correctly
- No relevant changes in the 2026.2.24-2026.2.26 changelog mention Telegram
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗