Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Discord typing indicator stops working after Discord outage/reconnect

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…

The Discord typing indicator stops being sent entirely after a Discord outage causes WebSocket disconnects and reconnect attempts. It does not recover even after the connection is re-established.

Error Message

[discord] channel resolve failed; Discord API /users/@me/guilds failed (500): 500: Internal Server Error

Root Cause

The Discord typing indicator stops being sent entirely after a Discord outage causes WebSocket disconnects and reconnect attempts. It does not recover even after the connection is re-established.

Fix Action

Fix / Workaround

  1. Discord experiences an outage causing WebSocket drops and failed API calls (500s, 504s, 429s on /gateway/bot)
  2. OpenClaw auto-reconnects successfully
  3. Typing indicator is no longer sent for any subsequent messages in that session
  4. Restarting the gateway does not fix it
  5. Setting agents.defaults.typingMode: instant via direct JSON edit (note: config.patch blocks this field) and restarting does not fix it
  • config.patch returns cannot change protected config paths: agents.defaults.typingMode — this seems unintentional given the field exists in the schema and the docs describe it as user-configurable
  • Two full gateway restarts after the outage did not restore typing indicator behavior
  • Messages are delivered successfully; only typing indicator is affected

Code Example

[discord] channel resolve failed; Discord API /users/@me/guilds failed (500): 500: Internal Server Error
[discord] channel resolve failed; Discord API /users/@me/guilds failed (504): Gateway time-out
[discord] gateway metadata lookup failed transiently; Discord API /gateway/bot failed (429): Service resource is being rate limited.
[discord] gateway: Gateway websocket closed: 1006
RAW_BUFFERClick to expand / collapse

Summary

The Discord typing indicator stops being sent entirely after a Discord outage causes WebSocket disconnects and reconnect attempts. It does not recover even after the connection is re-established.

Environment

  • OpenClaw: 2026.5.7 (eeef486)
  • Channel: Discord (direct message)
  • OS: macOS Darwin 25.3.0 (arm64)
  • Node: v24.14.1

Steps to Reproduce

  1. Discord experiences an outage causing WebSocket drops and failed API calls (500s, 504s, 429s on /gateway/bot)
  2. OpenClaw auto-reconnects successfully
  3. Typing indicator is no longer sent for any subsequent messages in that session
  4. Restarting the gateway does not fix it
  5. Setting agents.defaults.typingMode: instant via direct JSON edit (note: config.patch blocks this field) and restarting does not fix it

Observed Behavior

No typing indicator appears in Discord DMs. Gateway logs show zero typing-related entries after the outage, even for successful message processing turns. Previously the logs showed entries like typing TTL reached (2m); stopping typing indicator.

Expected Behavior

Typing indicator should resume after reconnect and/or gateway restart.

Log Evidence

During the outage (2026-05-08 ~14:40–14:43 MDT), multiple Discord errors were logged:

[discord] channel resolve failed; Discord API /users/@me/guilds failed (500): 500: Internal Server Error
[discord] channel resolve failed; Discord API /users/@me/guilds failed (504): Gateway time-out
[discord] gateway metadata lookup failed transiently; Discord API /gateway/bot failed (429): Service resource is being rate limited.
[discord] gateway: Gateway websocket closed: 1006

After reconnect, typing logs are completely absent. Last typing log entry was 2026-04-30 (prior to the outage day).

Additional Notes

  • config.patch returns cannot change protected config paths: agents.defaults.typingMode — this seems unintentional given the field exists in the schema and the docs describe it as user-configurable
  • Two full gateway restarts after the outage did not restore typing indicator behavior
  • Messages are delivered successfully; only typing indicator is affected

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…
#api#GPU compatibility#latency issue#model loading#dependency error

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 typing indicator stops working after Discord outage/reconnect