#Discord mentions intermittently not triggering agent replies in server channel (listener marked stuc

1 messages · Page 1 of 1 (latest)

oblique glen
#

In Discord server channel #charles (), mentioning the bot with @timid osprey is visible in channel history but often produces no response. DM responses work. This persisted after update + gateway restart.

Environment
OpenClaw: updated to latest (previously observed on 2026.3.1, update available to 2026.4.15)
OS: macOS arm64
Channel: Discord
Bot user: montgomerybot ()
Guild:
(#charles)

What I tested
Mentioned bot in channel using exact mention: @timid osprey ping
Confirmed mention appears in channel message history
Confirmed bot can send outbound message to same channel via tool/API
Restarted gateway and retested
Updated OpenClaw, restarted, retested
Problem persists

Expected
Mention in server channel triggers agent run and reply.

Actual
No reply for some mention events, even though message is present and mention resolves correctly.

Relevant log indicators
Repeated restarts: health-monitor: restarting (reason: stuck) for Discord provider
Slow listener warnings on Discord message events (DiscordMessageListener, MESSAGE_CREATE)
Bot login appears successful after restarts (logged in to discord as )
Impact
Unreliable bot responsiveness in server channels; DM path appears functional.

main sailBOT
torn pebbleBOT
#

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

main sailBOT
wet hatchBOT
#

This looks more like a Discord runtime/listener problem than a bad mention format.

Two big tells from your report:

  • health-monitor: restarting (reason: stuck) means the gateway thinks the Discord account is unhealthy and keeps recycling it.
  • If you’re seeing DiscordMessageListener ... timed out after 30000ms, that’s especially suspicious on current builds. Recent OpenClaw Discord changes made MESSAGE_CREATE handoff non-blocking, and the default listener budget is now 120000ms, not 30000ms.

So my first guess is: the running gateway is still effectively on an older/stale Discord runtime, or the Discord path is not picking up the newer queue settings.

Please paste these exact outputs:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw channels status --probe
#

And while reproducing one failed mention:

openclaw logs --follow

Then look for any of these:

  • discord: drop guild message ... → config/policy issue
  • message content intent / audit issues → Discord app config issue
  • Listener DiscordMessageListener timed out after 30000ms → likely stale runtime / old path
  • repeated reason: stuck with no mention-drop logs → provider/runtime health issue

Also verify in the Discord Developer Portal:

  • Message Content Intent = enabled
  • Server Members Intent = enabled