openclaw - ✅(Solved) Fix [Bug] Gateway timeout after 120ms blocks antfarm cron creation [1 pull requests, 2 comments, 1 participants]

jimbb · 2026-03-13T02:43:44Z

[openclaw] Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running au… Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running autonomously. # 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. ## Evidence - [x] Failing test/log before + passing after (New test `should handle 503 response gracefully without crashing` added to `provider.proxy.test.ts` which now passes.) - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: Added and passed a new unit test specifically for the 503 error case in `provider.proxy.test.ts`, ensuring the `response.ok` check and error handling logic are correctly implemented. - Edge cases checked: Specifically addressed the case where `response.json()` would throw an error on a non-2xx response. - What you did **not** verify: Did not verify in a live production environment with an actual Discord 503 error. ## Compatibility / Migration - Backward compatible? (`Yes`) - Config/env changes? (`No`) - Migration needed? (`No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: Revert this PR. - Files/config to restore: N/A - Known bad symptoms reviewers should watch for: Gateway still crashing on Discord 503, or Discord reconnection issues. ## Risks and Mitigations - Risk: The error handling or reconnection logic might not fully cover all edge cases of Discord API errors. - Mitigation: The current fix addresses the immediate crash by preventing `response.json()` on bad responses and uses existing reconnection mechanisms. Further monitoring of Discord integration health is always recommended. <img

openclaw2026-03-13 02:43:44

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#44562•Fetched 2026-04-08 00:45:12

View on GitHub

Comments

Participants

Timeline

Reactions

Author

jimbb

Participants

jimbb

Timeline (top)

commented ×2closed ×1cross-referenced ×1locked ×1

Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running autonomously.

Error Message

Cannot start workflow run: cron setup failed.
Failed to create cron job for agent "scanner":
CLI fallback failed: Error: gateway timeout after 120ms
Gateway target: ws://127.0.0.1:18789

Root Cause

OpenClaw CLI has a hardcoded 120ms timeout for gateway WebSocket connections. Real-world operations take 500ms-2000ms, especially when:

Gateway is under load
Multiple cron jobs created sequentially
System is resource-constrained

Code Example

Cannot start workflow run: cron setup failed.
Failed to create cron job for agent "scanner":
CLI fallback failed: Error: gateway timeout after 120ms
Gateway target: ws://127.0.0.1:18789

---

// Before
const WS_CONNECT_TIMEOUT_MS = 120;

// After  
const WS_CONNECT_TIMEOUT_MS = 10000; // 10 seconds

---

node ~/.openclaw/workspace/antfarm/dist/cli/cli.js workflow run security-audit "Test"
openclaw cron list | grep antfarm

RAW_BUFFERClick to expand / collapse

Summary

Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running autonomously.

Environment

OpenClaw: 2026.3.11
OS: Linux (VPS)
Node: v22.22.0
Gateway: local, loopback, token auth
Antfarm: 0.5.1

Problem

When starting an antfarm workflow, cron creation fails:

Antfarm tries HTTP POST to /tools/invoke
Falls back to OpenClaw CLI: openclaw cron add
CLI WebSocket connection times out after 120ms (too short)
Workflow fails to start

Error

Cannot start workflow run: cron setup failed.
Failed to create cron job for agent "scanner":
CLI fallback failed: Error: gateway timeout after 120ms
Gateway target: ws://127.0.0.1:18789

Root Cause

OpenClaw CLI has a hardcoded 120ms timeout for gateway WebSocket connections. Real-world operations take 500ms-2000ms, especially when:

Gateway is under load
Multiple cron jobs created sequentially
System is resource-constrained

Proposed Fix

Increase WebSocket connection timeout from 120ms to 10000ms (10 seconds).

Location: Likely in gateway client code Change:

// Before
const WS_CONNECT_TIMEOUT_MS = 120;

// After  
const WS_CONNECT_TIMEOUT_MS = 10000; // 10 seconds

Impact

Current: Antfarm workflows cannot start, CLI fallback unreliable After Fix: Workflows start successfully, better reliability on slower systems

Related Issues

#20288 - cron run WS timeout (30s)
#17000 - Sub-agent announcements timeout (60s)
#16729 - Gateway timeout causes message loss

Testing

node ~/.openclaw/workspace/antfarm/dist/cli/cli.js workflow run security-audit "Test"
openclaw cron list | grep antfarm

Priority: High - Blocks antfarm automation Severity: Major - Core functionality broken

extent analysis

Fix Plan

To resolve the issue, we need to increase the WebSocket connection timeout in the OpenClaw CLI. Here are the steps:

Locate the WS_CONNECT_TIMEOUT_MS constant in the gateway client code.
Update the value from 120 to 10000 (10 seconds) as shown below:

// Before
const WS_CONNECT_TIMEOUT_MS = 120;

// After
const WS_CONNECT_TIMEOUT_MS = 10000; // 10 seconds

Save the changes and rebuild the OpenClaw CLI.
Restart the Antfarm workflow to test the fix.

Verification

To verify that the fix worked, run the following commands:

node ~/.openclaw/workspace/antfarm/dist/cli/cli.js workflow run security-audit "Test"
openclaw cron list | grep antfarm

Check that the workflow starts successfully and the cron job is created without any errors.

Extra Tips

Monitor the system resources and gateway load to ensure that the increased timeout does not cause other issues.
Consider implementing a retry mechanism for WebSocket connections to improve reliability.
Review related issues (#20288, #17000, #16729) to ensure that similar timeouts are adjusted accordingly.

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?

#api #ssr #installation #tensor shape #autograd error #integration issue #index setup #retrieval issue #search optimization #API routing

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix [Bug] Gateway timeout after 120ms blocks antfarm cron creation [1 pull requests, 2 comments, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

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

Code Example

Summary

Environment

Problem

Error

Root Cause

Proposed Fix

Impact

Related Issues

Testing

extent analysis

Fix Plan

Verification

Extra Tips

Still need to ship something?

RELATED_DISCOVERY

TRENDING