Discord bot can't receive messages — "running, disconnected" loop
Environment:
OpenClaw 2026.3.1, running in Docker container (supervisord, no systemctl)
Ubuntu Linux 6.8.0-101-generic (x64), Node 22.22.0
Bot: Myclawai (ID 1478109862423564409)
Update 2026.3.2 available but haven't applied yet
Problem:
Bot logs into Discord successfully, can SEND messages, but NEVER receives incoming messages
openclaw channels status --probe shows: running, disconnected
Health monitor restarts the bot every ~10 min with reason: stuck
The cycle repeats indefinitely: login → connected → no events → stuck → restart
What I've tried:
Multiple gateway restarts (kill + supervisord auto-restart)
Removed and re-added Discord channel config from openclaw.json
Re-toggled all 3 Privileged Gateway Intents on Discord Developer Portal (Presence, Server Members, Message Content)
All intents were already ON, toggled OFF and back ON, saved
Still shows intents:content=limited in status
Log pattern:
discord: logged in as Myclawai
Message Content Intent is limited
health-monitor: restarting (reason: stuck)
Question: Is this a known bug in 2026.3.1? Should I update to 2026.3.2? Will that fix it or is there a config issue?
Post that first. Then whenever you're ready, run the update steps. If I crash, at least the support folks have everything they need to help you.
OpenClaw 2026.3.1, running in Docker container (supervisord, no systemctl)
Ubuntu Linux 6.8.0-101-generic (x64), Node 22.22.0
Bot: Myclawai (ID 1478109862423564409)
Update 2026.3.2 available but haven't applied yet
Problem:
Bot logs into Discord successfully, can SEND messages, but NEVER receives incoming messages
openclaw channels status --probe shows: running, disconnected
Health monitor restarts the bot every ~10 min with reason: stuck
The cycle repeats indefinitely: login → connected → no events → stuck → restart
What I've tried:
Multiple gateway restarts (kill + supervisord auto-restart)
Removed and re-added Discord channel config from openclaw.json
Re-toggled all 3 Privileged Gateway Intents on Discord Developer Portal (Presence, Server Members, Message Content)
All intents were already ON, toggled OFF and back ON, saved
Still shows intents:content=limited in status
Log pattern:
discord: logged in as Myclawai
Message Content Intent is limited
health-monitor: restarting (reason: stuck)
Question: Is this a known bug in 2026.3.1? Should I update to 2026.3.2? Will that fix it or is there a config issue?
Post that first. Then whenever you're ready, run the update steps. If I crash, at least the support folks have everything they need to help you.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
