Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Discord channel becomes `not configured, disabled` after upgrade

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

After upgrading OpenClaw from v2026.3.24 to a newer version, the Discord channel is no longer recognized as configured. The gateway can start successfully, but openclaw channels list --all reports Discord as:

Discord: installed, not configured, disabled

Root Cause

After upgrading OpenClaw from v2026.3.24 to a newer version, the Discord channel is no longer recognized as configured. The gateway can start successfully, but openclaw channels list --all reports Discord as:

Discord: installed, not configured, disabled

Code Example

Discord: installed, not configured, disabled

### Steps to reproduce

With a valid Discord config, OpenClaw should recognize Discord as configured and enabled.

Example config:

json

---

### Expected behavior

Expected output should indicate that Discord is configured/enabled, or at least not report it as not configured when a valid token is present.

### Actual behavior

After upgrading, the gateway starts, but Discord is shown as not configured and disabled:

---

This still happens if the token is configured as plaintext.

### OpenClaw version

2026.5.7

### Operating system

Ubuntu 24.04

### Install method

npm global

### Model

glm-5

### Provider / routing chain

openclaw - poe-provider - glm-5

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug: Discord channel becomes not configured, disabled after upgrade

Summary

After upgrading OpenClaw from v2026.3.24 to a newer version, the Discord channel is no longer recognized as configured. The gateway can start successfully, but openclaw channels list --all reports Discord as:

Discord: installed, not configured, disabled

### Steps to reproduce

With a valid Discord config, OpenClaw should recognize Discord as configured and enabled.

Example config:

json

{ "channels": { "discord": { "enabled": true, "token": "REDACTED_DISCORD_BOT_TOKEN", "groupPolicy": "allowlist", "guilds": { "xxx": { "requireMention": true, "users": [ "xxx" ] } } } } }


### Expected behavior

Expected output should indicate that Discord is configured/enabled, or at least not report it as not configured when a valid token is present.

### Actual behavior

After upgrading, the gateway starts, but Discord is shown as not configured and disabled:

Discord: installed, not configured, disabled

This still happens if the token is configured as plaintext.

### OpenClaw version

2026.5.7

### Operating system

Ubuntu 24.04

### Install method

npm global

### Model

glm-5

### Provider / routing chain

openclaw - poe-provider - glm-5

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected output should indicate that Discord is configured/enabled, or at least not report it as not configured when a valid token is present.

#api#ssr#installation#tensor shape#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Discord channel becomes `not configured, disabled` after upgrade