Discord gateway doesnt work doesnt matter what i try | Friends of the Crustacean 🦞🤝 | Page 1

copper blaze Apr 23, 2026, 1:39 PM

#

after i got the message „Discord inbound worker timed out.“ , my discord gateway stopped working. It doesnt matter what method I am trying it wont come back online. I even updated openclaw, restarted gateway, changed bot token and restarted my machine, nothing seems to be working.

opal girderBOT Apr 23, 2026, 1:39 PM

#

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

daring fableBOT Apr 23, 2026, 1:39 PM

#

static onyxBOT Apr 23, 2026, 1:40 PM

#

Exec approval is required, but native chat exec approvals are not configured on Discord.

Approve it from the Web UI or terminal UI for now. Discord supports native exec approvals for this account. Configure channels.discord.execApprovals.approvers or commands.ownerAllowFrom; leave channels.discord.execApprovals.enabled unset/auto or set it to true.

#

Let me check the docs and source so I don’t make up config keys.

static onyxBOT Apr 23, 2026, 1:42 PM

#

copper blaze after i got the message „Discord inbound worker timed out.“ , my discord gateway...

that’s frustrating. The exact Discord inbound worker timed out message is a real known symptom, especially with Discord threads and attachments, so you’re not imagining it.

Can you paste these 5 outputs first so we can separate “transport/auth is broken” from “Discord worker got wedged”:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw channels status --probe
openclaw logs --follow

Also tell me these 3 things:

Does the bot still show as online in Discord?
Did this start right after a thread message with an attachment/video/file?
Are DMs broken too, or only guild/thread messages?

#

Fast checks while you gather that:

In Discord Developer Portal, make sure Message Content Intent is still enabled.
Make sure the bot still has View Channels, Send Messages, Read Message History, and if you use threads, Send Messages in Threads.
If this was triggered by a thread attachment, try sending a plain text message in a DM or normal channel too. There’s a known thread/attachment hang issue.

Docs:

Likely relevant known bug if your logs match the 1800s hang:

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

Paste the outputs here and I’ll help narrow it down.

copper blaze Apr 23, 2026, 1:57 PM

#

static onyx Fast checks while you gather that: - In Discord Developer Portal, make sure **M...

just tell me how i can make this longer than 30 mins: Discord inbound worker timed out.

static onyxBOT Apr 23, 2026, 1:57 PM

#

set channels.discord.inboundWorker.runTimeoutMs.

For 1 hour:

{
  channels: {
    discord: {
      inboundWorker: {
        runTimeoutMs: 3600000, // 60 min
      },
    },
  },
}

For disable it entirely:

#

{
  channels: {
    discord: {
      inboundWorker: {
        runTimeoutMs: 0,
      },
    },
  },
}

If you use multi-account Discord, put it under the account instead:

#

  channels: {
    discord: {
      accounts: {
        default: {
          inboundWorker: {
            runTimeoutMs: 3600000,
          },
        },
      },
    },
  },
}

Then restart the gateway.

#

Also, if the thing actually timing out is the 30s listener, that is a different knob:

channels.discord.eventQueue.listenerTimeout

Docs section: https://docs.openclaw.ai/channels/discord

Small warning: this only makes the watchdog wait longer, it does not fix the underlying hang.

#Discord gateway doesnt work doesnt matter what i try