openclaw - 💡(How to fix) Fix [Bug]: [5.10-beta.5] Telegram Supergroup Forum Topics — Inbound Messages Not Processed [3 comments, 3 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

After updating from v2026.5.7 to v2026.5.10-beta.5 (1ba6893), the bot fails to process inbound messages from Telegram Supergroup Forum Topics. The "typing..." indicator appears, but no response is generated. Outbound messages work correctly.

Steps to reproduce

Environment

Configuration

{
  "telegram": {
    "enabled": true,
    "dmPolicy": "allowlist",
    "botToken": {
      "source": "env",
      "id": "TELEGRAM_BOT_TOKEN"
    },
    "allowFrom": [xxx],
    "groups": {
      "-xxx": {
        "requireMention": false,
        "topics": {
          "1": { "requireMention": false }
        }
      }
    },
    "groupPolicy": "allowlist",
    "streaming": { "mode": "partial" }
  }
}

Steps to Reproduce

1. Update OpenClaw from v2026.5.7 to v2026.5.10-beta.5 (even older version are not working!)
2. Configure Telegram Supergroup with Forum Topics (see config above)
3. Send message to Topic #1 (General) in Supergroup "KI-Chat X"
4. Observe ".... Bot typing..." appears briefly
5. Result No response generated, no session update, no logs

Expected Behavior

• Inbound message creates/updates session: agent:main:telegram:group:-xxx:topic:1
• Bot generates response in the same topic

Actual behavior

Actual Behavior

OpenClaw version

v2026.5.10-beta.5

Operating system

Ubuntu 22.04 LTS

Install method

npm

Model

ollama/kimi-k2.6:cloud

Provider / routing chain

Telegram → OpenClaw Gateway (self-hosted) → Ollama Cloud (kimi-k2.6)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

## Debug Information

### 1. Session Status

$ sessions_list --active 5min
→ Only Direct-Chat session visible
→ No Supergroup session created/updated


### 2. Command Logs

$ tail -5 ~/.openclaw/logs/commands.log
2026-05-12T15:23:45 → agent:main:telegram:group:-xxx:topic:1 (first message)
[No new entries for subsequent messages]


### 3. Telegram API Status

$ curl "https://api.telegram.org/bot$TOKEN/getChatMember?chat_id=-xxx&user_id=xxx"
→ Status: "administrator"
→ can_manage_topics: true
→ All permissions granted


### 4. Webhook/Polling Check

$ curl "https://api.telegram.org/bot$TOKEN/getWebhookInfo"
→ "url": "" (empty — using polling mode)
→ "pending_update_count": 0


### 5. Manual API Test

$ curl "https://api.telegram.org/bot$TOKEN/getUpdates?limit=10"
→ No updates visible for Supergroup messages
``

Impact and severity

Labels: bug, telegram, forum-topics, supergroup, inbound Priority: High — Breaks primary use case for group collaboration

Additional information

Hypotheses Tested

Related Issues (from Discord analysis by Kaspre)

• #17980 → fixed by commit e20b87f1b (Feb 16)
• #19144 → superseded by #19213, confirmed in v2026.2.19
• #18168 → resolved by #17980
• #14762 → auto-closed, consolidated to #15787

Note: All 4 issues above are closed. This appears to be a new or different regression.

Key Findings

1. Outbound delivery works — Bot can send messages to correct forum topic
2. Inbound processing fails — Messages from Supergroup Topics not received
3. Direct Chat unaffected — Private messages work normally
4. No error logs — Silent failure, no crash or error
5. "typing..." appears — Bot is online and connected, but doesn't receive message

Possible Root Causes

1. Polling offset issue — getUpdates offset skips Supergroup messages
2. Update filter — Polling excludes forum_topic or supergroup updates
3. Session routing — Inbound messages not routed to correct session key
4. Regression in beta — New change in 5.10-beta affecting topic handling