#Discord inbound worker timed out

1 messages · Page 1 of 1 (latest)

patent anchor
#

I’m using OpenClaw with discord client. Why am I getting this: “Discord inbound worker timed out.”?

static tulipBOT
frail lodgeBOT
#

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

obsidian gardenBOT
#

Let me check the docs and source for the exact error text.

#

What does openclaw --version show?

That exact message usually means OpenClaw killed a Discord turn because the queued inbound worker ran too long. It is usually not a Discord auth/client error.

The two timeout knobs are:

  • Worker timeout: channels.discord.inboundWorker.runTimeoutMs
  • Listener timeout: channels.discord.eventQueue.listenerTimeout

Defaults from the docs/source are:

  • inboundWorker.runTimeoutMs = 1800000 (30 min)
  • eventQueue.listenerTimeout = 120000 (120s)

So:

  • if it dies after a long time, it is usually inboundWorker.runTimeoutMs
#
  • if logs show ~120s, it is usually eventQueue.listenerTimeout

Common causes:

  • model/tool call hanging
  • slow browser/exec/web tool work
  • attachment processing stalling
  • provider/network issues that never finish cleanly

Good first checks:

openclaw status --all
openclaw logs --follow

If you want, paste:

  1. openclaw --version