openclaw - ✅(Solved) Fix [Bug]: Gateway crashes with unhandled promise rejection when Discord API returns 503 during health-monitor bot reconnect [4 pull requests, 3 comments, 3 participants]

j2j2j2j2j2j2j2j2 · 2026-03-13T01:54:11Z

[openclaw] When health-monitor restarts a stuck Discord bot connection and Discord API returns a 503 with non-JSON body, the gateway throws an unhandled promis… When health-monitor restarts a stuck Discord bot connection and Discord API returns a 503 with non-JSON body, the gateway throws an unhandled promise rejection and the entire Node.js process exits. # PR #44659: fix(discord): prevent gateway crash on non-JSON Discord API responses - Repository: openclaw/openclaw - Author: suboss87 - State: closed | merged: False - Link: https://github.com/openclaw/openclaw/pull/44659 ## Description (problem / solution / changelog) ## Summary Fixes a crash where a single Discord API 503 response kills the entire gateway process, taking all agents offline. - **Root cause**: `ProxyGatewayPlugin.registerClient()` calls `response.json()` without checking `response.ok` first. When Discord returns a 503 with a non-JSON body (e.g. `upstream connect error or disconnect/reset before headers`), `JSON.parse()` throws a `SyntaxError` that propagates as an unhandled promise rejection, crashing the Node.js process. - **Fix**: Add `response.ok` check before `.json()`, extract body safely with `.text().catch(() => "")`, and throw a descriptive error. This aligns with the existing pattern used throughout the Discord module (`api.ts`, `probe.ts`, `pluralkit.ts`). - **Tests added**: 3 new test cases covering 503, 502 (HTML body), and 500 (consumed body stream) scenarios. Existing happy-path test updated to include `ok: true` on the mock response. ## Impact - **Before**: One Discord 503 → entire gateway crashes → all agents (Discord, Slack, Telegram, etc.) go offline for 2-3 min until auto-restart - **After**: Error is caught and propagated cleanly through the existing error handling chain, allowing the health-monitor reconnect cycle to retry ## Test plan - [x] All 6 proxy gateway plugin tests pass (3 existing + 3 new) - [x] Full Discord test suite passes (576 tests) - [x] Linter passes (oxlint, 0 warnings) Closes #44529 ## Changed files - `src/discord/monitor/gateway-plugin.ts` (modified, +6/-0) - `src/discord/monitor/provider.proxy.test.ts` (modified, +67/-0) --- # PR #2: OpenClaw 紧急未修复 - Repository: haoruilee/openclaw - Author: haoruilee - State: closed | merged: False - Link: https://github.com/haoruilee/openclaw/pull/2 ## Description (problem / solution / changelog) ## Summary Describe the problem and fix in 2–5 bullets: - Problem: The Gateway crashes with an unhandled promise rejection when the Discord API returns a 503 error, as `response.json()` is called without checking `response.ok`. - Why it matters: This causes the entire gateway process to exit, leading to a complete service interruption for all connected Discord channels for several minutes. - What changed: Added a check for `response.ok` before attempting to parse the JSON response. Errors are now emitted via `this.emitter.emit("error")` and `this.handleReconnectionAttempt()` is called to trigger a graceful reconnection attempt, preventing a full process crash. Updated tests to cover the 503 error path. - What did NOT change (scope boundary): Other identified issues (#44544, #44611, #44562, #44549) were either already fixed, determined not to be code bugs, or required a dedicated test environment for safe implementation and are not part of this PR. ## Change Type (select all) - [x] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [x] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [x] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes #44529 - Related # ## User-visible / Behavior Changes The gateway will no longer crash when the Discord API returns a 503 error during client registration. Instead, it will log the error and attempt to reconnect gracefully. ## Security Impact (required) - New permissions/capabilities? (`No`) - Secrets/tokens handling changed? (`No`) - New/changed network calls? (`No`) - Command/tool execution surface changed? (`No`) - Data access scope changed? (`No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: Linux (typical Node.js environment) - Runtime/container: Node.js - Model/provider: N/A - Integration/channel (if any): Discord - Relevant config (redacted): N/A ### Steps 1. Configure OpenClaw Gateway with a Discord integration. 2. During the `GatewayPlugin.registerClient()` call (e.g., when the health monitor triggers a Discord bot reconnection), simulate a Discord API returning a 503 HTTP status code with a non-JSON body. 3. Observe the gateway process. ### Expected - The gateway logs an error about the Discord 503 response. - The gateway attempts to reconnect to Discord without crashing the entire Node.js process. ### Actual - The gateway process crashes with an unhandled promise rejection. ## E

openclaw2026-03-13 01:54:11

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#44529•Fetched 2026-04-08 00:45:41

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

cross-referenced ×4referenced ×4commented ×3labeled ×2

When health-monitor restarts a stuck Discord bot connection and Discord API returns a 503 with non-JSON body, the gateway throws an unhandled promise rejection and the entire Node.js process exits.

Error Message

[openclaw] Unhandled promise rejection: Error: Failed to get gateway information from Discord: Unexpected token 'u', "upstream c"... is not valid JSON at GatewayPlugin.registerClient (file:///opt/homebrew/lib/node_modules/openclaw/dist/subsystem-nlluZawe.js) at processTicksAndRejections (node:internal/process/task_queues:105:5)

Root Cause

When health-monitor restarts a stuck Discord bot connection and Discord API returns a 503 with non-JSON body, the gateway throws an unhandled promise rejection and the entire Node.js process exits.

Code Example

[openclaw] Unhandled promise rejection: Error: Failed to get gateway information from Discord: Unexpected token 'u', "upstream c"... is not valid JSON
    at GatewayPlugin.registerClient (file:///opt/homebrew/lib/node_modules/openclaw/dist/subsystem-nlluZawe.js)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)

---

Log sequence (timestamps in MYT):


04:20 [gateway/health-monitor] [discord:my-bot] health-monitor: restarting (reason: stuck)
04:21 [gateway/channels/discord] discord gateway: WebSocket connection closed with code 1006
04:30 [gateway/health-monitor] [discord:my-bot] health-monitor: restarting (reason: stuck)
04:30 [gateway/channels/discord] discord channel resolve failed; Discord API /channels/... failed (503): upstream connect error or disconnect/reset before headers. reset reason: overflow
04:30 [openclaw] Unhandled promise rejection: Error: Failed to get gateway information from Discord: Unexpected token 'u', "upstream c"... is not valid JSON
          at GatewayPlugin.registerClient
          at processTicksAndRejections (node:internal/process/task_queues:105:5)


bot-c was in a low-traffic channel and was flagged as stuck twice before the fatal crash on the second reconnect attempt. Discord status page showed no incidents.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

When health-monitor restarts a stuck Discord bot connection and Discord API returns a 503 with non-JSON body, the gateway throws an unhandled promise rejection and the entire Node.js process exits.

Steps to reproduce

Run gateway with multiple Discord bot accounts (bot-a, bot-b, bot-c)
One bot (aveline-bot) connection goes idle in a low-traffic channel
health-monitor detects stuck connection and triggers reconnect (reason: stuck)
During reconnect, Discord API returns HTTP 503 with non-JSON body: upstream connect error or disconnect/reset before headers. reset reason: overflow
GatewayPlugin.registerClient() attempts to parse the body as JSON
Unhandled promise rejection crashes the entire Node.js gateway process

Expected behavior

Gateway catches the 503 error gracefully, logs a warning, and retries the reconnect after backoff. The process should NOT exit.

Actual behavior

Gateway process exits with:

[openclaw] Unhandled promise rejection: Error: Failed to get gateway information from Discord: Unexpected token 'u', "upstream c"... is not valid JSON
    at GatewayPlugin.registerClient (file:///opt/homebrew/lib/node_modules/openclaw/dist/subsystem-nlluZawe.js)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)

LaunchAgent KeepAlive auto-restarts the gateway (~2-3 min downtime for all agents).

OpenClaw version

2026.3.2 (85377a2)

Operating system

macOS Sequoia (Apple Silicon M4)

Install method

npm global (homebrew node@22)

Model

anthropic/claude-sonnet-4-6

Provider / routing chain

openclaw -> anthropic (OAuth)

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Log sequence (timestamps in MYT):


04:20 [gateway/health-monitor] [discord:my-bot] health-monitor: restarting (reason: stuck)
04:21 [gateway/channels/discord] discord gateway: WebSocket connection closed with code 1006
04:30 [gateway/health-monitor] [discord:my-bot] health-monitor: restarting (reason: stuck)
04:30 [gateway/channels/discord] discord channel resolve failed; Discord API /channels/... failed (503): upstream connect error or disconnect/reset before headers. reset reason: overflow
04:30 [openclaw] Unhandled promise rejection: Error: Failed to get gateway information from Discord: Unexpected token 'u', "upstream c"... is not valid JSON
          at GatewayPlugin.registerClient
          at processTicksAndRejections (node:internal/process/task_queues:105:5)


bot-c was in a low-traffic channel and was flagged as stuck twice before the fatal crash on the second reconnect attempt. Discord status page showed no incidents.

Impact and severity

Affected: ALL agents on the gateway (not just aveline-bot)
Severity: High — entire gateway process exits, all agents go offline
Frequency: Intermittent (triggered by Discord API transient 503 during bot reconnect)
Consequence: ~2-3 minute outage for all agents; in-flight cron jobs interrupted; requires LaunchAgent/systemd for auto-recovery

Side note: health-monitor flagging an idle-but-alive bot as 'stuck' may itself be worth reviewing — bot-c was in a low-traffic channel with no recent messages.

Additional information

The unhandled rejection originates in GatewayPlugin.registerClient() when it calls the Discord gateway info endpoint and receives a non-JSON 503 response. Wrapping this call in try/catch (or adding a .catch() handler) and treating non-2xx or non-JSON responses as retriable errors would fix this.

No known workaround other than relying on LaunchAgent/systemd KeepAlive for auto-restart.

extent analysis

Fix Plan

To address the issue, we need to modify the GatewayPlugin.registerClient() method to handle non-JSON responses from the Discord API. We can achieve this by wrapping the API call in a try-catch block and adding a .catch() handler to catch any promise rejections.

Step-by-Step Solution

Modify the GatewayPlugin.registerClient() method:

// Before async function registerClient() { const response = await fetch('https://discord.com/api/gateway'); const jsonData = await response.json(); // ... }

// After async function registerClient() { try { const response = await fetch('https://discord.com/api/gateway'); if (!response.ok) { // Treat non-2xx responses as retriable errors throw new Error(HTTP error! status: ${response.status}); } const jsonData = await response.json(); // ... } catch (error) { // Log the error and retry the request after a backoff console.warn('Error registering client:', error); // Implement retry logic with backoff here } }


2. **Implement retry logic with backoff**:
   ```javascript
const retry = async (fn, retries = 3, delay = 500) => {
  let attempt = 0;
  while (attempt < retries) {
    try {
      return await fn();
    } catch (error) {
      attempt++;
      if (attempt < retries) {
        console.log(`Retry ${attempt} after ${delay}ms`);
        await new Promise(resolve => setTimeout(resolve, delay));
        delay *= 2; // exponential backoff
      } else {
        throw error;
      }
    }
  }
};

// Usage
async function registerClient() {
  await retry(async () => {
    // Original registerClient logic here
  });
}

Verification

To verify that the fix worked, you can simulate a non-JSON response from the Discord API and check that the gateway does not crash. You can also monitor the logs to ensure that the retry logic is working as expected.

Extra Tips

Make sure to handle errors properly and implement retry logic with backoff to avoid overwhelming the Discord API with requests.
Consider adding a circuit breaker pattern to detect when the Discord API is down and prevent further requests.
Review the health-monitor logic to prevent flagging idle-but-alive bots as 'stuck'.

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?

FAQ

Expected behavior

Gateway catches the 503 error gracefully, logs a warning, and retries the reconnect after backoff. The process should NOT exit.

#api #ssr #installation #tensor shape #autograd error #API versioning #request timeout

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix [Bug]: Gateway crashes with unhandled promise rejection when Discord API returns 503 during health-monitor bot reconnect [4 pull requests, 3 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

PR fix notes

PR #44659: fix(discord): prevent gateway crash on non-JSON Discord API responses

Description (problem / solution / changelog)

Summary

Impact

Test plan

Changed files

PR #2: OpenClaw 紧急未修复

Description (problem / solution / changelog)

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Changed files

PR #44669: fix(discord): prevent gateway crash when Discord API returns 503 during proxy reconnect, solve #44529

Description (problem / solution / changelog)

Summary

Root Cause

Fix

Before / After

Change Type

Scope

Linked Issue

User-visible / Behavior Changes

Security Impact

Repro + Verification

Changed files

PR #183: 🦅 Scout: Critical Inherited Defect Report - 2026-03-20

Description (problem / solution / changelog)

🦅 Scout Intelligence Report

Summary by CodeRabbit

Changed files

Code Example

Bug type

Summary

Steps to reproduce

Expected behavior

Actual behavior

OpenClaw version

Operating system

Install method

Model

Provider / routing chain

Config file / key location

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

Additional information

extent analysis

Fix Plan

Step-by-Step Solution

Verification

Extra Tips

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING