Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: gateway "ready" fires before acpx plugin finishes registering

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 gateway emits ready (6 plugins; 46.5s) before the acpx runtime backend has finished registering. The acpx plugin registers 58 seconds after the ready signal. Any client or subsystem that acts on gateway: ready as a reliable "all systems go" signal will attempt to use acpx before it's available, causing silent failures or hangs.

Root Cause

The gateway emits ready (6 plugins; 46.5s) before the acpx runtime backend has finished registering. The acpx plugin registers 58 seconds after the ready signal. Any client or subsystem that acts on gateway: ready as a reliable "all systems go" signal will attempt to use acpx before it's available, causing silent failures or hangs.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

Yes

Summary

The gateway emits ready (6 plugins; 46.5s) before the acpx runtime backend has finished registering. The acpx plugin registers 58 seconds after the ready signal. Any client or subsystem that acts on gateway: ready as a reliable "all systems go" signal will attempt to use acpx before it's available, causing silent failures or hangs.

Steps to reproduce

  1. Start the gateway cold (openclaw gateway start)
  2. Watch the log for gateway: ready
  3. Note the timestamp
  4. Watch for plugins: embedded acpx runtime backend registered
  5. Observe: acpx registers ~58s after ready was declared

Expected behavior

gateway: ready should not fire until all declared plugins have completed initialization. If a plugin exceeds a timeout threshold, it should be flagged as degraded — not silently excluded from the ready signal.

Actual behavior

The gateway emits ready (6 plugins; 46.5s) before the acpx runtime backend has finished registering. The acpx plugin registers 58 seconds after the ready signal. Any client or subsystem that acts on gateway: ready as a reliable "all systems go" signal will attempt to use acpx before it's available, causing silent failures or hangs.

OpenClaw version

2026.5.7

Operating system

Windows 11 (10.0.26200, x64)

Install method

No response

Model

openai/gpt-5.4

Provider / routing chain

openai → gpt-5.4

Additional provider/model setup details

No response

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

gateway: ready should not fire until all declared plugins have completed initialization. If a plugin exceeds a timeout threshold, it should be flagged as degraded — not silently excluded from the ready signal.

#pipeline error#runtime error#dependency conflict#environment setup#docker 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 [Bug]: gateway "ready" fires before acpx plugin finishes registering