#discord slash commands fail

1 messages · Page 1 of 1 (latest)

inner wharf
#

Apr 19 05:43:07 openclaw1 node[90009]: 2026-04-19T05:43:07.859+00:00 Cannot access rawData on partial Channel. Use fetch() to populate data.
Apr 19 05:43:07 openclaw1 node[90009]: 2026-04-19T05:43:07.860+00:00 Error: Cannot access rawData on partial Channel. Use fetch() to populate data.
Apr 19 05:43:07 openclaw1 node[90009]: at GuildTextChannel.get rawData [as rawData] (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/abstracts/BaseChannel.ts:65:10)
Apr 19 05:43:07 openclaw1 node[90009]: at GuildTextChannel.get name [as name] (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/abstracts/BaseGuildChannel.ts:28:13)
Apr 19 05:43:07 openclaw1 node[90009]: at dispatchDiscordCommandInteraction (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/extensions/discord/provider-D8OJvlaj.js:2409:61)
Apr 19 05:43:07 openclaw1 node[90009]: at Command.run (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/extensions/discord/provider-D8OJvlaj.js:2366:10)
Apr 19 05:43:07 openclaw1 node[90009]: at processTicksAndRejections (node:internal/process/task_queues:104:5)
Apr 19 05:43:07 openclaw1 node[90009]: at CommandHandler.handleCommandInteraction (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/internals/CommandHandler.ts:173:19)
Apr 19 05:43:07 openclaw1 node[90009]: at Client.handleInteraction (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/classes/Client.ts:481:9)
Apr 19 05:43:07 openclaw1 node[90009]: at InteractionEventListener.handle (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/plugins/gateway/InteractionEventListener.ts:9:3)
Apr 19 05:43:07 openclaw1 node[90009]: at EventQueue.processListener (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/internals/EventQueue.ts:365:4)
Apr 19 05:43:07 openclaw1 node[90009]: at runNext (file:///home/openclaw/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/@buape/carbon/src/internals/EventQueue.ts:327:5)

ancient quiverBOT
spiral ermineBOT
#

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

ancient quiverBOT
plush burrowBOT
#

Let me check the docs and the Discord code path. This smells like a partial-channel object getting dereferenced during slash command dispatch, not a bad user config.

#

That looks like a real bug in the Discord slash-command path, not a bad config.

OpenClaw is reading interaction.channel.name from a partial channel object, and Carbon throws exactly what you pasted. I traced it to the Discord native-command handler, so this is likely code-side, not something you misconfigured. It may show up more often in threads.

Can you paste these next:

openclaw --version
openclaw status --all

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/gateway/troubleshooting

Temporary workaround, try the same slash command in a normal channel or DM if possible, or use non-slash message routing for now.

#

If you're already on the latest build and it still repros, please file an issue with:

  • exact slash command
  • whether it only fails in threads
  • that stack trace
  • openclaw --version

Paste the version/output here and I’ll help narrow it down further. 🦐

inner wharf
#

openclaw@openclaw1:~/.openclawopenclaw --versionon
OpenClaw 2026.4.19-beta.1 (4862d34)

# 

Gateway connection details:
  Gateway target: ws://127.0.0.1:18789
  Source: local loopback
  Config: /home/openclaw/.openclaw/openclaw.json
  Bind: lan

✓ Config: /home/openclaw/.openclaw/openclaw.json
✓ Secret diagnostics (0)
✓ Restart sentinel: none
! Port 18789
  Port 18789 is already in use.
  - pid 90009 openclaw: openclaw-gateway (*:18789)
  - Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
! Tailscale: off · unknown
✓ Skills: 15 eligible · 0 missing · /home/openclaw/.openclaw/workspace
✓ Plugin compatibility (none)

Gateway restart attempts (tail): /home/openclaw/.openclaw/logs/gateway-restart.log
  [2026-04-19T05:41:20Z] openclaw restart attempt source=update target=openclaw-gateway.service
  [2026-04-19T05:41:20Z] openclaw restart done source=update
✓ Channel issues (none)```
plush burrowBOT
#

Nice, thanks, that helps. 2026.4.19-beta.1 is current enough that this does not look like an "old version" problem.

This really looks like a Discord slash-command bug/regression in OpenClaw. The handler is touching interaction.channel.name before the partial channel gets fetched/populated, so Carbon blows up.

So, a few concrete takeaways:

  • I do not think this is a config mistake on your side.
  • I do not think openclaw status --all is going to reveal much here.
  • I do think this needs a code fix.

One useful check, if you want to narrow it fast:

  • does the same slash command fail only in this thread, or also in a normal top-level text channel?

If it is thread-only, that fits this bug really well.

For now, workaround is:

  • run the slash command in a normal channel/DM if that works, or
#
  • use normal message/mention-based interaction instead of slash commands

Since this needs maintainer attention, please open an issue with:

  • your version: OpenClaw 2026.4.19-beta.1 (4862d34)
  • the stack trace
  • the exact slash command
  • whether it is thread-only or everywhere

Issue tracker:
https://github.com/openclaw/openclaw/issues

If you test top-level channel vs thread and paste the result, I can help tighten the repro before you file it.

#

Yep, that diagnosis looks clean.

A few notes from it:

  • Port 18789 already in use is expected here. It just means the gateway is already running.
  • Channel issues (none) points away from Discord auth/pairing/config trouble.
  • The restart log just shows the gateway restarted after the update.

So this still looks like a current slash-command bug/regression, not a setup problem on your box.

At this point, the most useful next step is a GitHub issue with:

  • OpenClaw 2026.4.19-beta.1 (4862d34)
  • the stack trace
  • that diagnosis output
  • the exact slash command you ran
  • whether it happens only in help/forum threads, or also in a normal text channel