Description

After upgrading to OpenClaw 2026.6.11, Feishu direct messages intermittently fail with:

Error: reply session initialization conflicted for agent:evo:feishu:direct:<redacted>

The error occurs in bursts after gateway restart, then self-resolves after retries. It does not block all messages — the current session eventually works.

Environment

• OpenClaw version: 2026.6.11
• Feishu plugin: @openclaw/feishu (bundled with 2026.6.11)
• OS: Linux (x64)
• Node: v24.16.0
• Feishu connection mode: websocket
• Config: dmPolicy=pairing, renderMode=default

Steps to Reproduce

1. Restart the gateway
2. Send messages via Feishu DM within the first few minutes after restart
3. Observe the gateway log

Actual Behavior

Multiple messages fail with "reply session initialization conflicted" before eventually succeeding:

diagnostic: message dispatch completed: channel=feishu outcome=error
  error="Error: reply session initialization conflicted for agent:<agent>:feishu:direct:<chat_id>"

diagnostic: message processed: channel=feishu outcome=error
  error="Error: reply session initialization conflicted for agent:<agent>:feishu:direct:<chat_id>"

channels/feishu: feishu[default]: failed to dispatch message:
  Error: reply session initialization conflicted for agent:<agent>:feishu:direct:<chat_id>

In the same log window, we also see the related pattern from #87468:

queuedFinal=false, replies=0

Expected Behavior

Messages should dispatch reliably on first attempt without session initialization conflicts.

Additional Context

• This appears to be a race condition in session initialization after gateway restart
• The error is transient — subsequent messages in the same session eventually work
• May be related to Feishu: Agent-generated replies silently dropped (replies=0, queuedFinal=false) after WebSocket reconnect #87468 (Feishu replies silently dropped after WebSocket reconnect) — both involve the dispatch pipeline failing to properly initialize or route to the reply session
• Also observed queuedFinal=false, replies=0 alongside this error, suggesting a shared root cause in the Feishu reply delivery path