Summary

When blockStreaming: true is set on the Discord channel config, normal assistant replies (conversational responses) silently fail to deliver after the first successful reply. This affects both guild channels and DMs. The message send tool continues to work correctly throughout.

Environment

• OpenClaw version: 2026.2.23 (npm, macOS arm64)
• Node.js: v25.6.1
• Channel: Discord (observed in both guild channels and DMs)
• Discord config:

  {
    "blockStreaming": true,
    "blockStreamingCoalesce": { "idleMs": 1500 },
    "streamMode": "off"
  }

Steps to Reproduce

1. Configure a Discord channel with blockStreaming: true and blockStreamingCoalesce.idleMs: 1500
2. Reboot machine
3. Send a message to the bot (in a guild channel or DM)
4. The first normal reply after a fresh gateway start is delivered successfully
5. Send another message — the assistant generates a reply, but it never appears in Discord
6. All subsequent normal replies are silently dropped
7. Using the message tool (action: send) to the same channel works every time

Expected Behavior

All normal assistant replies should be delivered to Discord consistently, regardless of how many have been sent since startup.

Actual Behavior

• ✅ First reply after a full machine reboot: delivered
• ❌ All subsequent normal replies: silently dropped (no error surfaced in gateway.log)
• ✅ message send tool: always works
• Observed in both guild channels and DMs

Additionally, gateway.err.log shows DiscordMessageListener timeouts around the time the issue occurs. Their relationship to the root cause is unclear, but included for context:

[EventQueue] Slow listener detected: DiscordMessageListener took 36 seconds for event MESSAGE_CREATE
[EventQueue] Listener DiscordMessageListener timed out after 30000ms for event MESSAGE_CREATE
[discord] Slow listener detected: DiscordMessageListener took 80.7 seconds for event MESSAGE_CREATE

Troubleshooting Attempted

• Gateway restart (SIGUSR1): Did not resolve the issue — no replies delivered at all, not even the first
• Full machine reboot: Temporarily resolved it (first reply delivered, then subsequent replies dropped again)
• npm i -g openclaw@latest: Re-installed latest (2026.2.23), 694 packages changed — did not resolve

Workaround

Setting blockStreaming: false resolves the issue — all normal replies deliver correctly and consistently.

{ "channels": { "discord": { "blockStreaming": false } } }