Bug Description
After upgrading to OpenClaw 2026.5.4, Feishu bot accounts intermittently fail to send replies. Messages are received and processed by agents, but dispatch complete (queuedFinal=false, replies=0) and no message is sent to Feishu.
This affects both group chats and DM (p2p) sessions — it is not limited to group chat, though it is more prevalent there.
Reproduction Steps
- Send any message to a Feishu bot (DM or group)
- Observe the gateway log:
feishu[account]: dispatch complete (queuedFinal=false, replies=0)
- No reply appears in Feishu
Affected accounts: happylife, capital-market, history-research, lc, macmini (all DM and group paths)
Root Cause Analysis
The bug is in the OpenClaw core reply dispatch mechanism:
- When a message triggers a reply without a streaming card, the reply dispatcher's
counts.final remains 0
- Messages with
Started Streaming card → replies=1 ✅
- Messages without streaming card → replies=0 ❌
Evidence from gateway logs (macmini DM path):
# Working (with streaming)
Started Streaming: cardId=..., messageId=om_...
dispatch complete (queuedFinal=true, replies=2)
Closed streaming
# Broken (without streaming)
DM from ou_...: [message content]
dispatching to agent
dispatch complete (queuedFinal=false, replies=0) ← no streaming card
Timeline
- May 05 08:33 UTC+8: Gateway restart loaded openclaw 2026.5.4
- May 05 17:07: Last capital-market success before failure
- May 05 18:25: capital-market first
replies=0
- May 05 21:35: macmini first
replies=0 in DM
- May 06 06:43: Feishu plugin reverted to 2026.5.3 — issue persists
- May 06: openclaw 2026.5.4 still running — issue persists
Version Info
- openclaw: 2026.5.4 (installed May 05 via auto-update)
- @openclaw/feishu: 2026.5.3 (reverted from 2026.5.4, did not fix)
- macOS: Darwin 25.4.0 (arm64)
- Node: v25.6.1
Related Issues
Expected Behavior
Every message that triggers an agent response should result in replies>=1 in the gateway log and a reply sent to Feishu, regardless of whether a streaming card is used.
Possible Cause
The counts.final logic in the core dispatch module may be incorrectly gated on streaming card presence. When a reply is generated without a streaming card (i.e., a simple text reply), the reply dispatcher is not being properly settled/queued, resulting in queuedFinal=false and replies=0.
Bug Description
After upgrading to OpenClaw 2026.5.4, Feishu bot accounts intermittently fail to send replies. Messages are received and processed by agents, but
dispatch complete (queuedFinal=false, replies=0)and no message is sent to Feishu.This affects both group chats and DM (p2p) sessions — it is not limited to group chat, though it is more prevalent there.
Reproduction Steps
feishu[account]: dispatch complete (queuedFinal=false, replies=0)Affected accounts: happylife, capital-market, history-research, lc, macmini (all DM and group paths)
Root Cause Analysis
The bug is in the OpenClaw core reply dispatch mechanism:
counts.finalremains 0Started Streamingcard → replies=1 ✅Evidence from gateway logs (macmini DM path):
Timeline
replies=0replies=0in DMVersion Info
Related Issues
Expected Behavior
Every message that triggers an agent response should result in
replies>=1in the gateway log and a reply sent to Feishu, regardless of whether a streaming card is used.Possible Cause
The
counts.finallogic in the core dispatch module may be incorrectly gated on streaming card presence. When a reply is generated without a streaming card (i.e., a simple text reply), the reply dispatcher is not being properly settled/queued, resulting inqueuedFinal=falseandreplies=0.