4 people reported
All time, since Oct 2.
Cloud environment fails capability query and cannot resume
“At approximately 15:44 UTC, cloud startup failed with failed to query executor configuration capabilities for environment.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9164/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Commands are rejected before execution with "No usable execution environment is available" after the cloud environment reports failed.
Is this your bug?
File my report- Where
- Codex Cloud executor
- Error text
failed to query executor configuration capabilities- Platforms
- macOS, Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Not quite your bug?
- Cloud workspace files lost5 people
- Cloud task loses workspace2 people
- Dot cloud task create and continue fail with UNKNOWN18 people
Original reports4, newest first
- Codex Cloud: snapshot restoration exhausts retries; environment draft save returns HTTP 500On GitHub#53102
- [Dots] Cloud computer unusable: exec-server disconnected, capability query failed, no usable execution environmentOn GitHub#52531
- [Dots] Cloud executor stops responding and cannot resume after file-transfer timeoutOn GitHub#52509
- Codex Cloud: existing sessions fail to start and environment editing is blockedOn the forum#1402870