Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Bug Report: Discord message tool send fails with "Unknown Channel" in 2026.5.4
OpenClaw version: 2026.5.4 (upgraded from 2026.5.2)
Runtime: Docker on TerraMaster NAS (F2-425), host network
Channel: Discord (bot token, DM-only, allowFrom configured)
Summary
The message tool action=send to Discord fails consistently with "Unknown Channel", even though:
- The bot receives Discord DMs correctly (user can message the bot and I respond)
openclaw channels resolve discord:1439091261670948987 correctly resolves the user ID
- Cron job
announce delivery sometimes works (some Rheinmetall reports were delivered)
- Bot is connected and shows
OK in openclaw status
Steps to reproduce
Steps to reproduce
-
Configure Discord channel with bot token, dmPolicy: allowlist, allowFrom: ["<user_id>"]
-
Attempt to send a DM using the message tool:
-
Result: Unknown Channel error
Expected behavior
Expected behavior
Message should be delivered to the user's Discord DM.
Actual behavior
From gateway log:
[tools] message failed: Unknown Channel raw_params={"action":"send","message":"...","target":"1439091261670948987"}
Note: channels.resolve works fine:
discord:1439091261670948987 -> 1439091261670948987
Additional context
- This persisted through upgrade from 2026.5.2 → 2026.5.4
- Restarting the gateway does not fix it
- Cron
announce delivery to the same Discord user sometimes works, sometimes fails
- The bot is confirmed connected — user is actively messaging it right now
Suggested investigation
The discrepancy between:
channels.resolve succeeding (user ID is valid)
message send failing (Unknown Channel)
- cron announce delivery sometimes succeeding
suggests the issue may be in how the message tool routes the target parameter vs. how the cron announce delivery resolves it. Possibly the tool's Discord send path is not using the resolved user ID correctly.
OpenClaw version
2026.5.4
Operating system
Linux 6.1.120+ x64
Install method
Docker ghcr.io/openclaw/openclaw:2026.5.4
Model
minimax/MiniMax-M2.7
Provider / routing chain
discord:1439091261670948987 (bot token, DM-only)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Bug Report: Discord
messagetool send fails with "Unknown Channel" in 2026.5.4OpenClaw version: 2026.5.4 (upgraded from 2026.5.2)
Runtime: Docker on TerraMaster NAS (F2-425), host network
Channel: Discord (bot token, DM-only, allowFrom configured)
Summary
The
messagetoolaction=sendto Discord fails consistently with"Unknown Channel", even though:openclaw channels resolve discord:1439091261670948987correctly resolves the user IDannouncedelivery sometimes works (some Rheinmetall reports were delivered)OKinopenclaw statusSteps to reproduce
Steps to reproduce
Configure Discord channel with bot token,
dmPolicy: allowlist,allowFrom: ["<user_id>"]Attempt to send a DM using the
messagetool:Result:
Unknown ChannelerrorExpected behavior
Expected behavior
Message should be delivered to the user's Discord DM.
Actual behavior
From gateway log:
[tools] message failed: Unknown Channel raw_params={"action":"send","message":"...","target":"1439091261670948987"}
Note:
channels.resolveworks fine:discord:1439091261670948987 -> 1439091261670948987
Additional context
announcedelivery to the same Discord user sometimes works, sometimes failsSuggested investigation
The discrepancy between:
channels.resolvesucceeding (user ID is valid)message sendfailing (Unknown Channel)suggests the issue may be in how the
messagetool routes thetargetparameter vs. how the cron announce delivery resolves it. Possibly the tool's Discord send path is not using the resolved user ID correctly.OpenClaw version
2026.5.4
Operating system
Linux 6.1.120+ x64
Install method
Docker ghcr.io/openclaw/openclaw:2026.5.4
Model
minimax/MiniMax-M2.7
Provider / routing chain
discord:1439091261670948987 (bot token, DM-only)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response