openclaw - 💡(How to fix) Fix Discord inbound messages not reaching agent after gateway reconnects [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75346Fetched 2026-05-01 05:34:54
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
3
Timeline (top)
mentioned ×2subscribed ×2commented ×1

Discord inbound delivery appears unreliable on Ben's Mac Studio OpenClaw gateway. User reports Q is not receiving Discord messages. Local WebChat is working.

Root Cause

Discord inbound delivery appears unreliable on Ben's Mac Studio OpenClaw gateway. User reports Q is not receiving Discord messages. Local WebChat is working.

Code Example

2026-04-30T15:44:58.722-07:00 [discord] gateway: Gateway websocket closed: 1006
2026-04-30T15:44:58.728-07:00 [discord] gateway: Gateway reconnect scheduled in 1107ms (close, resume=true)
2026-04-30T16:00:53.616-07:00 [discord] gateway: Gateway websocket closed: 1000
2026-04-30T16:00:53.616-07:00 [discord] gateway: Gateway reconnect scheduled in 916ms (close, resume=true)
2026-04-30T17:32:37.613-07:00 [discord] gateway: Gateway websocket closed: 1006
2026-04-30T17:32:37.614-07:00 [discord] gateway: Gateway reconnect scheduled in 1131ms (close, resume=true)
2026-04-30T18:30:30.937-07:00 [discord] gateway: Gateway websocket closed: 1000
2026-04-30T18:30:30.938-07:00 [discord] gateway: Gateway reconnect scheduled in 951ms (close, resume=true)
RAW_BUFFERClick to expand / collapse

Summary

Discord inbound delivery appears unreliable on Ben's Mac Studio OpenClaw gateway. User reports Q is not receiving Discord messages. Local WebChat is working.

Environment

  • Host: Mac-Studio
  • OpenClaw: 2026.4.25 (gateway log reports update available 2026.4.29)
  • Runtime node: Darwin arm64 / Node v22.22.1
  • Discord config: enabled, allowlist guild/channel config, requireMention=true for configured channels

Evidence from local logs

Recent gateway log shows repeated Discord websocket closes/reconnects:

2026-04-30T15:44:58.722-07:00 [discord] gateway: Gateway websocket closed: 1006
2026-04-30T15:44:58.728-07:00 [discord] gateway: Gateway reconnect scheduled in 1107ms (close, resume=true)
2026-04-30T16:00:53.616-07:00 [discord] gateway: Gateway websocket closed: 1000
2026-04-30T16:00:53.616-07:00 [discord] gateway: Gateway reconnect scheduled in 916ms (close, resume=true)
2026-04-30T17:32:37.613-07:00 [discord] gateway: Gateway websocket closed: 1006
2026-04-30T17:32:37.614-07:00 [discord] gateway: Gateway reconnect scheduled in 1131ms (close, resume=true)
2026-04-30T18:30:30.937-07:00 [discord] gateway: Gateway websocket closed: 1000
2026-04-30T18:30:30.938-07:00 [discord] gateway: Gateway reconnect scheduled in 951ms (close, resume=true)

openclaw status also hangs/times out locally rather than returning quickly. Watchdog previously reported /opt/homebrew/bin/openclaw status timed out after 45s.

Process sample at report time showed openclaw-gateway consuming high CPU (~39%) and large RSS (~2.5GB).

Expected

Discord gateway remains connected or self-heals after close/reconnect events, and allowlisted/mentioned Discord messages are enqueued to the agent.

Actual

User reports no inbound Discord messages are reaching Q. Logs show reconnects but no obvious inbound message handling after the report.

Initial suspicion

Could be one of:

  • Discord gateway reconnect/resume state goes stale after close 1000/1006.
  • Main gateway event loop is wedged or overloaded enough that Discord receives are dropped/delayed.
  • CLI/status path shares a stuck internal dependency and health checks are masking a degraded gateway.
  • Existing 2026.4.29 Discord/gateway fixes may already address part of this; needs verification on Ben's config.

Acceptance / test queue

  1. Apply candidate fix or upgrade path.
  2. Restart gateway safely.
  3. Ben sends a test message in the allowlisted Discord channel with required mention.
  4. Q confirms receipt and replies from Discord.
  5. openclaw status returns within 10s.

Assign/owner: Q / Ben testing queue.

extent analysis

TL;DR

Upgrade to OpenClaw version 2026.4.29 to potentially address Discord gateway reconnect and message handling issues.

Guidance

  • Verify the Discord gateway reconnect/resume state is not causing the issue by checking the gateway logs for any patterns or errors after reconnects.
  • Check the system resources (CPU and memory) to ensure the openclaw-gateway process is not overloaded, which could be causing dropped or delayed Discord receives.
  • Test the openclaw status command to see if it returns quickly after upgrading to the new version, indicating a potential fix for the stuck internal dependency.
  • Apply the upgrade and follow the acceptance/test queue steps to verify the fix.

Notes

The current issue may be related to a known problem that is fixed in the upcoming version 2026.4.29, but this needs to be verified on Ben's specific configuration.

Recommendation

Apply the workaround by upgrading to OpenClaw version 2026.4.29, as it may address the Discord gateway reconnect and message handling issues, and then follow the acceptance/test queue steps to verify the fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Discord inbound messages not reaching agent after gateway reconnects [1 comments, 2 participants]