Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

On OpenClaw 2026.5.12 (f066dd2), Discord inbound still works but outbound final replies and announce-style deliveries intermittently fail or remain queued, with evidence of Outbound not configured for channel: discord.

Steps to reproduce

1. Run OpenClaw 2026.5.12 (f066dd2) on Linux with Discord channel plugin configured and connected for channel 12345.
2. Send a normal Discord message in #main-conversation (channel ID 12345) that should trigger an agent reply.
3. Observe reply behavior across multiple attempts:
   • Some replies appear in ControlUI session only.
   • Some replies appear in Discord with delayed timing (minutes).
4. Check pending outbound queue on host:
   • ls ~/.openclaw/delivery-queue | wc -l shows persistent non-zero backlog (observed: 8–9 pending files during incident window spanning 47 hours).
5. Inspect queued payload/error content and runtime logs:
   • queued delivery entries include Outbound not configured for channel: discord.
   • historical runtime evidence includes Unsupported channel: discord in the same failure family.

Expected behavior

With Discord plugin connected and inbound events processed, final assistant replies and announce deliveries should post reliably to the same Discord channel without multi-minute delay or queue accumulation.

Actual behavior

Observed mixed behavior in same channel/session window:

• Discord inbound is received.
• Some outbound replies do post (including delayed post at 15:56 for a 15:54 response).
• Other outbound replies stay visible only in ControlUI and do not post to Discord.
• Delivery queue remains stuck with Discord-targeted pending items and Outbound not configured for channel: discord.

OpenClaw version

2026.5.12 (f066dd2)

Operating system

Ubuntu 24.04 LTS (Linux x86_64)

Install method

npm global; gateway process on host

Model

openai-codex/gpt-5.5

Provider / routing chain

OpenClaw gateway -> OpenAI Codex provider

Additional provider/model setup details

Model/provider path appears healthy; failure manifests in outbound channel delivery path. Direct message sends can succeed while generic final-reply/announce path remains inconsistent, suggesting channel outbound registration/resolution drift rather than provider failure.

Logs, screenshots, and evidence

# runtime version
OpenClaw 2026.5.12 (f066dd2)

# queue depth observed during incident verification
$ ls -1 ~/.openclaw/delivery-queue 2>/dev/null | wc -l
9

# representative queued error text observed in discord-targeted delivery entries:
Error: Outbound not configured for channel: discord

Timeline evidence (Europe/Berlin):
User Discord message: say hi / message ID 123456
Outbound inconsistency observed in same channel (12345)
One historic message eventually broke through to Discord
One assistant reply timestamped ~15:54 became visible in Discord at ~15:56
Related closed issue:
#77254 (closed + locked): similar root symptom family; this report confirms persistence/regression on 2026.5.12.

Impact and severity

Affected: Discord channel users (#main-conversation) relying on normal conversational replies and announce/final delivery paths. Severity: High (message-loss perception and delayed/partial delivery in production chat workflow). Frequency: Intermittent but recurrent in observed window (mix of success, delay, and silent non-delivery). Consequence: Lost trust in channel reliability, missed/late responses, operational confusion between ControlUI and Discord outputs.

Additional information

The best match closed issue #77254 (Discord outbound delivery loses adapter after plugin registry reload), and its described errors are the same pair I observed. Related open issues (#54745, #57491, #55437, #1530, #76217) show the same broader failure family: outbound adapter/plugin resolution breaks while channel/plugin appears loaded.