Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Control UI webchat request timeout aborts all fallback candidates before embedded Codex run starts [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#83962•Fetched 2026-05-20 03:45:57
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
1
Author
castorle7-rgbcastorle7-rgb
Participants
castorle7-rgbcastorle7-rgbclawsweeper[bot]clawsweeper[bot]
Timeline (top)
labeled ×4mentioned ×2subscribed ×2commented ×1

After upgrading from 2026.5.7 to 2026.5.18, Control UI webchat can fail with:

Agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

The important part is that every fallback candidate receives the same abort/timeout almost immediately. In the failing run, the normal agent/embedded strict-agentic execution contract active log line never appears, suggesting the webchat request timeout fires before the embedded Codex run actually starts.

Error Message

2026-05-19T12:21:37.979+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.5 reason=timeout errorPreview="This operation was aborted" 2026-05-19T12:21:39.104+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.3-codex reason=timeout errorPreview="This operation was aborted" 2026-05-19T12:21:47.128+09:00 warn model-fallback/decision runId=77b298a8... candidate=qwen-portal/coder-model reason=timeout errorPreview="This operation was aborted" 2026-05-19T12:21:48.303+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.2 reason=timeout errorPreview="This operation was aborted" 2026-05-19T12:21:49.876+09:00 error Embedded agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

Root Cause

After upgrading from 2026.5.7 to 2026.5.18, Control UI webchat can fail with:

Agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

The important part is that every fallback candidate receives the same abort/timeout almost immediately. In the failing run, the normal agent/embedded strict-agentic execution contract active log line never appears, suggesting the webchat request timeout fires before the embedded Codex run actually starts.

Code Example

Agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

---

2026-05-19T12:20:00.052+09:00 info gateway/ws webchat connected conn=d7441f25... client=openclaw-control-ui webchat vcontrol-ui
2026-05-19T12:20:01.764+09:00 info gateway/ws ⇄ res ✓ health 592ms cached=true
2026-05-19T12:20:07.727+09:00 info gateway/ws ⇄ res ✓ commands.list 5125ms
2026-05-19T12:20:07.787+09:00 info gateway/ws ⇄ res ✓ models.list 5184ms
2026-05-19T12:20:08.020+09:00 info gateway/ws ⇄ res ✓ sessions.list 5420ms
2026-05-19T12:20:08.760+09:00 info gateway/ws ⇄ res ✓ chat.history 6160ms
2026-05-19T12:20:09.054+09:00 info gateway/ws ⇄ res ✓ models.authStatus 6454ms

2026-05-19T12:21:37.979+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.5 reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:39.104+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.3-codex reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:47.128+09:00 warn model-fallback/decision runId=77b298a8... candidate=qwen-portal/coder-model reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:48.303+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.2 reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:49.876+09:00 error Embedded agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

---

openclaw agent --agent main --message 'Reply with exactly: OK' --model openai/gpt-5.5 --timeout 180 --json
# status: ok, provider: openai-codex, model: gpt-5.5, fallbackUsed: false
RAW_BUFFERClick to expand / collapse

Summary

After upgrading from 2026.5.7 to 2026.5.18, Control UI webchat can fail with:

Agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

The important part is that every fallback candidate receives the same abort/timeout almost immediately. In the failing run, the normal agent/embedded strict-agentic execution contract active log line never appears, suggesting the webchat request timeout fires before the embedded Codex run actually starts.

Environment

  • OpenClaw: 2026.5.18 (50a2481)
  • macOS: 15.7.4
  • Node: v22.22.0
  • Control UI: openclaw-control-ui webchat vcontrol-ui
  • Model config: openai/gpt-5.5
  • Runtime provider in logs: openai-codex/gpt-5.5
  • OAuth/auth-profile mode

Reproduction path observed

  1. Restart gateway.
  2. Fully quit browser, reopen Control UI, reload.
  3. Send a webchat message from Control UI.
  4. The run eventually returns All models failed (4) with timeout/aborted for every fallback candidate.

Relevant logs

2026-05-19T12:20:00.052+09:00 info gateway/ws webchat connected conn=d7441f25... client=openclaw-control-ui webchat vcontrol-ui
2026-05-19T12:20:01.764+09:00 info gateway/ws ⇄ res ✓ health 592ms cached=true
2026-05-19T12:20:07.727+09:00 info gateway/ws ⇄ res ✓ commands.list 5125ms
2026-05-19T12:20:07.787+09:00 info gateway/ws ⇄ res ✓ models.list 5184ms
2026-05-19T12:20:08.020+09:00 info gateway/ws ⇄ res ✓ sessions.list 5420ms
2026-05-19T12:20:08.760+09:00 info gateway/ws ⇄ res ✓ chat.history 6160ms
2026-05-19T12:20:09.054+09:00 info gateway/ws ⇄ res ✓ models.authStatus 6454ms

2026-05-19T12:21:37.979+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.5 reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:39.104+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.3-codex reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:47.128+09:00 warn model-fallback/decision runId=77b298a8... candidate=qwen-portal/coder-model reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:48.303+09:00 warn model-fallback/decision runId=77b298a8... candidate=openai/gpt-5.2 reason=timeout errorPreview="This operation was aborted"
2026-05-19T12:21:49.876+09:00 error Embedded agent failed before reply: All models failed (4): openai/gpt-5.5: This operation was aborted (timeout) | openai/gpt-5.3-codex: This operation was aborted (timeout) | qwen-portal/coder-model: This operation was aborted (timeout) | openai/gpt-5.2: This operation was aborted (timeout)

Expected behavior

If the first candidate is slow or not started yet, fallback candidates should not all be immediately aborted by the same already-fired webchat abort signal. Either the webchat request timeout should be long enough for agent startup, or fallback should use a fresh per-candidate timeout/abort controller.

Additional notes

CLI runs using the same OpenAI OAuth/Codex harness succeed, which suggests this is not an OAuth or model availability problem:

openclaw agent --agent main --message 'Reply with exactly: OK' --model openai/gpt-5.5 --timeout 180 --json
# status: ok, provider: openai-codex, model: gpt-5.5, fallbackUsed: false

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

If the first candidate is slow or not started yet, fallback candidates should not all be immediately aborted by the same already-fired webchat abort signal. Either the webchat request timeout should be long enough for agent startup, or fallback should use a fresh per-candidate timeout/abort controller.

#authentication issue#prompt issue#agent setup#task chaining#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING