Bug type

Regression (worked before, now fails)

Summary

Environment

• OpenClaw: 2026.3.2
• macOS, gateway: local (LaunchAgent)
• Two Telegram accounts: process_main (@Process_main1987_bot), xiaohuang (@Xiaohuang998_bot)
• Bindings: main → process_main, work → xiaohuang
• Group: DZ-pokerV3, chat id -5065715577

Steps to reproduce

Problem

• Messages in the group are received (visible in UI / “有录入”).
• Bot never replies in the group (no sendMessage to -5065715577 in logs after one success at 10:53).
• There was one successful telegram sendMessage ok chat=-5065715577 message=81 earlier; after that only lane wait exceeded: lane=session:agent:main:telegram:group:-5065715577 or no relevant log when sending in group.
• Private chat (6059784801) works; sendMessage to that chat appears in logs.

Expected behavior

Config (redact tokens)

• channels.telegram.groupPolicy: "open"
• channels.telegram.groups: { "*": { "requireMention": false }, "-5065715577": { "requireMention": false } }
• channels.telegram.accounts.process_main.groups: { "-5065715577": { "requireMention": false } }
• agents.defaults.maxConcurrent: 10
• Session agent:main:telegram:group:-5065715577 has deliveryContext.accountId: "process_main", to: "telegram:-5065715577"
• Bot privacy mode: Disabled in BotFather for both bots

Actual behavior

• Session agent:main:telegram:group:-5065715577 has deliveryContext.accountId: "process_main", to: "telegram:-5065715577"
• Bot privacy mode: Disabled in BotFather for both bots

Log snippet (after sending one message in group with gateway running)

# Paste here: grep -E "5065715577|sendMessage|lane|telegram" /tmp/openclaw/openclaw-$(date +%Y-%m-%d).log | tail -30

Related

• Likely related to main/session lane concurrency: Message Processing Bottleneck with Multiple Telegram Bots (main lane concurrency limit) #16055
• Session lane for group has only one slot; after one run blocks or times out, no sendMessage to group.

OpenClaw version

3.2

Operating system

macOS 4.2

Install method

npm

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response