#🐛 Discord channel stuck on "awaiting gateway readiness" — OpenClaw 2026.4.8

1 messages · Page 1 of 1 (latest)

sonic crystal
#

Setup: OpenClaw 2026.4.8 running in Docker on Synology NAS (920+). WhatsApp channel works perfectly.
Problem: Discord bot connects and shows online (green) in server, but never receives the READY event. Stuck permanently at:
[discord] client initialized as <bot_id> (Todd); awaiting gateway readiness
What I've confirmed:

✅ All three Privileged Gateway Intents enabled (Presence, Server Members, Message Content)
✅ Bot token is valid and correct
✅ discord.com and gateway.discord.gg both reachable from container (HTTP 200)
✅ Bot shows as online/green in Discord server
✅ DISCORD_BOT_TOKEN set as environment variable
✅ Tried with and without DISCORD_APPLICATION_ID env var
✅ Tried OPENCLAW_NO_BONJOUR=true — Bonjour still runs, no effect
❌ No Discord session cache files found to clear
❌ No inbound messages ever registered in logs

Log snippet on every startup:
[discord] [default] Discord Message Content Intent is limited; bots under 100 servers can use it without verification.
[discord] [default] starting provider (@Todd)
[discord] client initialized as <id> (Todd); awaiting gateway readiness
Then nothing. Ever.
Question: Is this the known "Carbon Reconcile" hang in 2026.4.x? Any workaround short of downgrading to 2026.3.13?

pine oceanBOT
flint narwhalBOT
#

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

pine oceanBOT
stoic oarBOT
#

I’m checking the Discord startup path in source now, because the “online but never READY” detail is the important bit here.

#

I checked the docs and the v2026.4.8 source specifically.

Short version, this looks like the same Discord/Carbon startup family, but not a “known forever hang” that 2026.4.8 should silently sit in.

In v2026.4.8, if READY never lands, OpenClaw is supposed to do this automatically:

  • after ~15s: restart the Discord gateway
  • after ~30s: log an error like
    discord gateway opened but did not reach READY within 30000ms

So if you only ever see:

client initialized as <id> (Todd); awaiting gateway readiness

and then nothing else, I’d suspect one of these:

  1. the container is not actually running the bits you think it is
#
  1. you are not seeing the later Discord gateway status/error output

A couple verified details:

  • DISCORD_APPLICATION_ID is not required for this path. OpenClaw fetches the app ID itself.
  • OPENCLAW_NO_BONJOUR is unrelated here.

My recommendation is upgrade forward, not downgrade.

Relevant follow-up fixes landed right after 4.8:

  • 2026.4.10 includes an update carbon
  • 2026.4.12 includes fix(discord): clear stale heartbeat timers in SafeGatewayPlugin.connect()

So if you want the practical workaround, I’d jump to >= 2026.4.12, ideally current 2026.4.x, before trying 2026.3.13.

First things I’d want from inside the container:

# 
openclaw --version
openclaw channels status --probe
openclaw status --deep
openclaw logs --follow

On a broken READY path, I’d expect to see one of these within ~30s:

  • discord: gateway was not ready after 15000ms; restarting gateway
  • discord gateway opened but did not reach READY within 30000ms

If you paste those outputs, especially openclaw --version and openclaw channels status --probe, I can narrow it down pretty fast.

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