Summary
After upgrading from v2026.3.1 to v2026.3.2, all Feishu bot accounts fail to send replies. Messages are received and processed by agents, but outbound delivery shows replies=0 with no error logs. Rolling back to v2026.3.1 immediately resolves the issue.
Environment
- OpenClaw: v2026.3.2 (regression from v2026.3.1)
- Channel: Feishu (WebSocket mode)
- OS: Linux 6.8.0-71-generic (x64)
- Node: v22.22.0
- Install method: pnpm global
Configuration
Multiple Feishu bot accounts configured:
- feishu[default] → agent:main
- feishu[assistant] → agent:assistant
- feishu[clerk] → agent:clerk
- feishu[manager] → agent:manager
Steps to Reproduce
- Start from working v2026.3.1 installation with Feishu bots
- Run
openclaw update to upgrade to v2026.3.2
- Send DM message to any Feishu bot account
- Observe gateway logs
Expected Behavior
- Agent receives message and generates reply
- Reply is sent back to Feishu user
- Gateway log shows
dispatch complete (queuedFinal=false, replies=1)
Actual Behavior
- Agent receives message and generates reply (confirmed in session logs)
- Reply is NOT sent to Feishu user
- Gateway log shows
dispatch complete (queuedFinal=false, replies=0)
- No error messages in gateway logs
Log Evidence
feishu[default]: received message from ou_98c54a3d8c4a45b9a4d6de76eabcf291 in oc_e32878ccee133f0297f7df137555c353 (p2p)
feishu[default]: dispatching to agent (session=agent:main:main)
feishu[default]: dispatch complete (queuedFinal=false, replies=0)
Session logs confirm reply was generated but never sent.
Root Cause Analysis
Likely introduced by one of these v2026.3.2 PRs:
Workaround
Roll back to v2026.3.1:
openclaw update --tag 2026.3.1 --yes
Related Issues
Summary
After upgrading from v2026.3.1 to v2026.3.2, all Feishu bot accounts fail to send replies. Messages are received and processed by agents, but outbound delivery shows
replies=0with no error logs. Rolling back to v2026.3.1 immediately resolves the issue.Environment
Configuration
Multiple Feishu bot accounts configured:
Steps to Reproduce
openclaw updateto upgrade to v2026.3.2Expected Behavior
dispatch complete (queuedFinal=false, replies=1)Actual Behavior
dispatch complete (queuedFinal=false, replies=0)Log Evidence
Session logs confirm reply was generated but never sent.
Root Cause Analysis
Likely introduced by one of these v2026.3.2 PRs:
Workaround
Roll back to v2026.3.1:
Related Issues