-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
Codex app-server startup retries can exhaust before replacement server is ready #83959
Copy link
Copy link
Open
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:crash-loopCrash, hang, restart loop, or process-level availability failure.Crash, hang, restart loop, or process-level availability failure.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:crash-loopCrash, hang, restart loop, or process-level availability failure.Crash, hang, restart loop, or process-level availability failure.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Priority
None yet
Summary
On OpenClaw
v2026.5.18, a scheduled background agent turn using the Codex harness failed during app-server startup with:The local logs showed repeated startup-close handling in the same shape:
After the retry budget was exhausted, a later turn succeeded shortly afterward, which suggests the replacement app-server may still have been warming up when the immediate retries ran.
Impact
A scheduled/background turn can fail before reaching user work, even though the Codex route becomes viable moments later. This is especially noisy for cron-style automation because it reports a job failure even when there is no task-level or repository-level problem.
Expected behavior
When the app-server connection closes during startup, OpenClaw should tolerate a short replacement-server warm-up window before declaring the Codex harness failed.
Useful behavior would be:
Local mitigation tested
A local mitigation increased the startup-close retry budget and added a short bounded backoff between startup retry attempts. After restarting the gateway, a trivial Codex agent smoke test completed successfully and no new startup-close exhaustion was observed.
Related
Possibly related to #79495, which covers shared Codex app-server client eviction across agents. This issue is narrower: even when restarting the app-server is the intended recovery path, the startup retry loop can exhaust before the replacement process is ready.