Error while using /model on Discord channel | Friends of the Crustacean 🦞🤝 | Page 1

molten dune Apr 21, 2026, 10:13 PM

#

The error message:

9:11:31 Cannot access rawData on partial Channel. Use fetch() to populate data.
19:11:31 Error: Cannot access rawData on partial Channel. Use fetch() to populate data.
    at GuildThreadChannel.get rawData [as rawData] (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/node_modules/@buape/carbon/src/abstracts/BaseChannel.ts:65:10)
    at GuildThreadChannel.get parentId [as parentId] (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/node_modules/@buape/carbon/src/abstracts/BaseGuildChannel.ts:44:13)
    at dispatchDiscordCommandInteraction (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/provider-CraktAkD.js:2451:47)
    at processTicksAndRejections (node:internal/process/task_queues:104:5)
    at Command.run (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/provider-CraktAkD.js:2367:4)
    at CommandHandler.handleCommandInteraction (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/node_modules/@buape/carbon/src/internals/CommandHandler.ts:173:19)
    at Client.handleInteraction (file:///home/wh1te/.volta/tools/image/packages/openclaw/lib/node_modules/openclaw/dist/extensions/discord/node_modules/@buape/carbon/src/classes/Client.ts:481:9)

It continues into a long error message. What should I do? How can I report it?

tight chasmBOT Apr 21, 2026, 10:13 PM

#

elfin spindleBOT Apr 21, 2026, 10:13 PM

#

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

tight chasmBOT Apr 21, 2026, 10:13 PM

#

hot currentBOT Apr 21, 2026, 10:16 PM

#

This looks like a real OpenClaw bug, not something you did wrong. The crash is happening in Discord slash-command handling for a thread/partial channel object.

I found a very recent repo fix named fix: tolerate partial discord channel metadata (#68953), so the first thing I’d try is:

openclaw --version
openclaw update

Then retry /model.

If it still happens, please file a GitHub issue here:

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

Include these in the report:

#

openclaw --version
exact repro steps, for example: “run /model inside a Discord thread/forum post”
the full stack trace
openclaw status --all
OS + install method
whether it also fails in a DM or normal channel, or only in threads

Useful commands:

openclaw status --all
openclaw logs --follow

Then trigger /model again and copy the relevant log block.

Temporary workaround, try /model in a DM or non-thread channel. The trace specifically points at thread parent metadata.

#

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/install/updating

If you paste your openclaw --version here, I can help tell whether you’re likely already on a version with that fix.

molten dune Apr 21, 2026, 10:18 PM

#

My version is OpenClaw 2026.4.20 (115f05d)

hot currentBOT Apr 21, 2026, 10:19 PM

#

Nice, that helps.

OpenClaw 2026.4.20 (115f05d) is already pretty recent, so I would treat this as a bug report now, not just a local setup issue.

I also found this in the changelog for newer changes:

Discord/slash commands: tolerate partial Discord channel metadata in slash-command and model-picker flows so partial channel objects no longer crash when channel names, topics, or thread parent metadata are unavailable. (#68953)

That’s basically the same bug family as your stack trace, so one of these is true:

your build does not include that fix yet, or
this is a remaining edge case

What I’d do

1) Quick workaround

Try /model in:

#

a DM
a normal channel
not inside a thread/forum post

If it only breaks in threads, that’s great signal for the report.

2) Collect a clean repro bundle

Run:

openclaw status --all
openclaw logs --follow

Then trigger /model again and copy the relevant log block.

status --all is the right thing to share, the FAQ explicitly calls it a safe pasteable report with tokens redacted:

#

https://docs.openclaw.ai/help/faq

3) File the issue

Open it here:

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

Suggested title:

Discord /model in thread crashes with Cannot access rawData on partial Channel

Suggested body:

Version: OpenClaw 2026.4.20 (115f05d)

#

Repro:
1. Open a Discord thread / forum post
2. Run `/model`
3. Observe crash

Expected:
`/model` opens or switches models normally

Actual:
OpenClaw throws:
`Cannot access rawData on partial Channel. Use fetch() to populate data.`

Stack trace:
[paste full stack trace]

#

Also tested:
- DM: [works/fails]
- normal channel: [works/fails]
- thread/forum post: [works/fails]

Diagnostics:
[paste `openclaw status --all`]
[paste relevant `openclaw logs --follow` output]

If you want, paste whether it fails in DM / normal channel / thread only, and I can help tighten the repro before you file it.

molten dune Apr 22, 2026, 12:30 AM

#

Has a fix been released as a beta version already? It only happens on threads

hot currentBOT Apr 22, 2026, 12:31 AM

#

I just checked the current changelog, and no, I don’t see that fix in a released beta yet.

The partial-Discord-thread fix, #68953, is still listed under Unreleased, not under a numbered beta release. So I would assume 2026.4.20 does not have it yet.

Your extra detail is really useful: “only happens on threads” matches the fix description almost exactly.

What I’d do now

Report it on GitHub: https://github.com/openclaw/openclaw/issues
Mention:
- OpenClaw 2026.4.20 (115f05d)
- Discord
- /model
- only reproducible in threads/forum posts
- normal channel / DM behavior, if you tested those

Suggested title:

#

Discord /model fails in threads with Cannot access rawData on partial Channel

If you want to try an unreleased build sooner, the likely path is dev/main, not beta:

openclaw update --channel dev

Docs: https://docs.openclaw.ai/install/updating

So short version: not in beta yet, report it now, and note that it is thread-only. That should make triage much faster.

If you want, I can help you write a clean issue body you can paste directly.

molten dune Apr 22, 2026, 12:32 AM

#

To which version should I downgrade to fix it? It happens with any slash command and I cannot switch models or thinking level of a specific thread except from openclaw.json.

hot currentBOT Apr 22, 2026, 12:34 AM

#

I wouldn’t downgrade blind here. I don’t have a verified good downgrade target, and the changelog points to a forward fix that is still unreleased.

The better workaround is:

Option 1, easiest

Use those commands from a normal channel or DM, not a thread.

Option 2, better thread workaround

Disable Discord native commands and use text commands instead.

Per docs, Discord supports:

commands.text: true (default)
channels.discord.commands.native: false

So you can set:

#

{
  channels: {
    discord: {
      commands: {
        native: false
      }
    }
  }
}

Then restart OpenClaw.

After that, use plain text messages in the thread like:

#

/model
/model openai/gpt-5.4
/think high
/reasoning on

That gives you per-thread/session overrides without editing openclaw.json every time.

Important: this means normal text commands, not Discord’s native slash picker.

Docs:
https://docs.openclaw.ai/tools/slash-commands

So short version:

No downgrade recommendation from me

#

Use non-thread channels, or
Turn off native Discord commands and use text commands in threads

If you want, I can help you with the exact config change + restart steps.

molten dune Apr 22, 2026, 12:36 AM

#

This is so weird because the bot can answer normally but not to slash commands, however slash commands don't trigger a crash either, so you can continue to chat after that. Weird. I'm too lazy (and busy) to log-in on GitHub to make a bug report right now, so what should I do? Is it ok if I don't report it now?

#Error while using /model on Discord channel