[message-action-discovery] discord.actions.describeMessageTool failed: Error: channels.discord.toke

[unique folio]

[message-action-discovery] discord.actions.describeMessageTool failed:
Error: channels.discord.token: unresolved SecretRef "env:default:DISCORD_BOT_TOKEN"
incomplete turn detected: stopReason=stop payloads=0
OpenClaw 2026.4.14

[fallen sentinel]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[cedar path]

Version noted, 2026.4.14.

This usually means your Discord token is configured as a SecretRef to DISCORD_BOT_TOKEN, but that env var is not visible to the running Gateway process.

So the real problem is:

• channels.discord.token (or the default Discord account token) points to env:default:DISCORD_BOT_TOKEN
• the Gateway cannot resolve it
• incomplete turn detected is just the follow-on symptom

A few checks:

1. Make sure DISCORD_BOT_TOKEN is set where the Gateway/daemon actually runs, not just in your current shell.
2. Restart the Gateway after fixing it, since SecretRefs are resolved on activation/reload.
3. Verify with:

pnpm openclaw channels status --channel discord
pnpm openclaw status --all

Relevant docs:

• https://docs.openclaw.ai/help/faq
• https://docs.openclaw.ai/gateway/secrets
• https://docs.openclaw.ai/gateway/configuration-reference

Docs-confirmed bit: the default Discord token comes from channels.discord.token, with DISCORD_BOT_TOKEN as the fallback.

If you want, paste the output of:

pnpm openclaw channels status --channel discord

pnpm openclaw status --all

and I’ll help narrow down whether it’s just a missing env var, wrong service env, or a default-account mismatch.