openclaw - 💡(How to fix) Fix [Bug]: Discord voice /vc join fails on Windows with AggregateError + gateway heartbeat timeout / event loop starvation [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#80344Fetched 2026-05-11 03:15:53
View on GitHub
Comments
1
Participants
2
Timeline
13
Reactions
2
Timeline (top)
subscribed ×5mentioned ×4labeled ×2commented ×1

OpenClaw 2026.5.7 (eeef486) OS: Windows

channels.discord.voice: { "enabled": true, "connectTimeoutMs": 60000, "reconnectGraceMs": 60000 }

Voice channel permissions verified OK:

  • ViewChannel
  • Connect
  • Speak
  • SendMessages
  • ReadMessageHistory
  • UseVAD
  • Administrator

Relevant logs: discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout discord gateway: Gateway websocket closed: 1006 fetch timeout reached; eventLoopDelayHint="timer delayed ..., likely event-loop starvation"

Other symptoms:

  • openclaw channels capabilities --channel discord --target channel:1491755095950364715 hangs and eventually SIGKILLs
  • openclaw gateway restart --force fails on Windows with TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGUSR1
  • Bot may briefly connect to voice and then leave, or fail before ready

Error Message

discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout discord voice: join failed before ready: guild <id> channel <id>timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout The gateway should not block the event loop, lose the Discord gateway heartbeat, or close the Discord websocket while attempting to join voice. Diagnostic commands such as openclaw channels capabilities --channel discord --target channel:<voice-channel-id> should complete or fail with a clear error instead of hanging/SIGKILLing. On Windows, openclaw gateway restart --force should restart or report an actionable Windows-safe error, not fail with ERR_UNKNOWN_SIGNAL: Unknown signal: SIGUSR1. discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError

  • discord gateway error: Error: Gateway heartbeat ACK timeout

Root Cause

OpenClaw 2026.5.7 (eeef486) OS: Windows

channels.discord.voice: { "enabled": true, "connectTimeoutMs": 60000, "reconnectGraceMs": 60000 }

Voice channel permissions verified OK:

  • ViewChannel
  • Connect
  • Speak
  • SendMessages
  • ReadMessageHistory
  • UseVAD
  • Administrator

Relevant logs: discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout discord gateway: Gateway websocket closed: 1006 fetch timeout reached; eventLoopDelayHint="timer delayed ..., likely event-loop starvation"

Other symptoms:

  • openclaw channels capabilities --channel discord --target channel:1491755095950364715 hangs and eventually SIGKILLs
  • openclaw gateway restart --force fails on Windows with TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGUSR1
  • Bot may briefly connect to voice and then leave, or fail before ready
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

OpenClaw 2026.5.7 (eeef486) OS: Windows

channels.discord.voice: { "enabled": true, "connectTimeoutMs": 60000, "reconnectGraceMs": 60000 }

Voice channel permissions verified OK:

  • ViewChannel
  • Connect
  • Speak
  • SendMessages
  • ReadMessageHistory
  • UseVAD
  • Administrator

Relevant logs: discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout discord gateway: Gateway websocket closed: 1006 fetch timeout reached; eventLoopDelayHint="timer delayed ..., likely event-loop starvation"

Other symptoms:

  • openclaw channels capabilities --channel discord --target channel:1491755095950364715 hangs and eventually SIGKILLs
  • openclaw gateway restart --force fails on Windows with TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGUSR1
  • Bot may briefly connect to voice and then leave, or fail before ready

Steps to reproduce

  1. Run OpenClaw on Windows: openclaw --version OpenClaw 2026.5.7 (eeef486)

  2. Configure Discord voice: channels.discord.voice = { "enabled": true, "connectTimeoutMs": 60000, "reconnectGraceMs": 60000 }

  3. Ensure the Discord bot is invited to the server with the required scopes, including:

    • bot
  • applications.commands
  1. Ensure the bot has the required permissions in the target voice channel:

    • ViewChannel
    • Connect
    • Speak
    • SendMessages
    • ReadMessageHistory
    • UseVAD
    • Administrator was also present during testing
  2. Restart the OpenClaw gateway.

  3. In the Discord server, run: /vc join channel:<id>

  4. Observe that the bot either briefly joins and leaves, or fails before reaching Ready.

  5. Check logs and observe: discord voice: join failed before ready: guild <id> channel <id>timeout=60000ms error=AggregateError discord gateway error: Error: Gateway heartbeat ACK timeout discord gateway: Gateway websocket closed: 1006 fetch timeout reached; eventLoopDelayHint="timer delayed ..., likely event-loop starvation"

  6. Optional related repros:

    • Run openclaw channels capabilities --channel discord --target channel:<id>; it hangs and eventually gets SIGKILLed.
    • Run openclaw gateway restart --force on Windows; it fails with TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGUSR1.

Expected behavior

When running /vc join for a Discord voice channel where the bot has the required permissions, OpenClaw should join the voice channel and remain connected/ready for voice interaction.

The gateway should not block the event loop, lose the Discord gateway heartbeat, or close the Discord websocket while attempting to join voice. Diagnostic commands such as openclaw channels capabilities --channel discord --target channel:<voice-channel-id> should complete or fail with a clear error instead of hanging/SIGKILLing.

On Windows, openclaw gateway restart --force should restart or report an actionable Windows-safe error, not fail with ERR_UNKNOWN_SIGNAL: Unknown signal: SIGUSR1.

Actual behavior

Running /vc join does not result in a stable Discord voice connection.

Observed behavior varies between attempts:

  • The bot sometimes briefly joins the voice channel and then immediately leaves.
  • Other attempts fail before the voice connection reaches Ready.
  • The latest failure shows: discord voice: join failed before ready: guild 1491755094864302223 channel 1491755095950364715 timeout=60000ms error=AggregateError

At the same time, the gateway logs show Discord/gateway instability:

  • discord gateway error: Error: Gateway heartbeat ACK timeout
  • discord gateway: Gateway websocket closed: 1006
  • fetch timeout reached; eventLoopDelayHint="timer delayed ..., likely event-loop starvation" Related diagnostics also behave unexpectedly:
  • openclaw channels capabilities --channel discord --target channel:1491755095950364715 hangs and eventually gets SIGKILLed.
  • On Windows, openclaw gateway restart --force fails with: TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGUSR1

The voice channel permissions appear correct, so this does not look like a simple Discord permission/channel override issue.

OpenClaw version

2026.5.7

Operating system

Windows 11 pro

Install method

npm global

Model

codex gpt 5.5

Provider / routing chain

Discord official bot gateway → OpenClaw Discord channel plugin → Discord voice /vc handler → @discordjs/voice joinVoiceChannel No extra proxy or custom gateway is intentionally configured. The bot token is configured through channels.discord, and /vc is being invoked from the Discord server. The failing path appears to be the Discord voice join/ready handshake, not an LLM/model provider request.

Additional provider/model setup details

No model request is reached during the failing join attempt; the failure happens before the voice connection reaches Ready.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

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…

FAQ

Expected behavior

When running /vc join for a Discord voice channel where the bot has the required permissions, OpenClaw should join the voice channel and remain connected/ready for voice interaction.

The gateway should not block the event loop, lose the Discord gateway heartbeat, or close the Discord websocket while attempting to join voice. Diagnostic commands such as openclaw channels capabilities --channel discord --target channel:<voice-channel-id> should complete or fail with a clear error instead of hanging/SIGKILLing.

On Windows, openclaw gateway restart --force should restart or report an actionable Windows-safe error, not fail with ERR_UNKNOWN_SIGNAL: Unknown signal: SIGUSR1.

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 [Bug]: Discord voice /vc join fails on Windows with AggregateError + gateway heartbeat timeout / event loop starvation [1 comments, 2 participants]