Title: Codex Cloud tasks inaccessible after environment recreation; FailedPrecondition errors and missing Python dependencies
I’m experiencing persistent Codex Cloud reliability problems that have interrupted development across two GitHub repositories.
There are two related symptoms:
1. Existing Codex tasks cannot be opened or resumed
Previously accessible tasks now display errors such as:
- “Codex could not open this task. Try again in a moment.”
- “FailedPrecondition: The cloud build for this thread has been deleted and cannot be resumed.”
The failure affects access to existing tasks, not simply execution of new commands. I’m particularly concerned about whether saved task conversation history remains recoverable independently of the Cloud execution environment.
2. Published environment dependencies do not persist into fresh tasks
In a separate but related issue, a published Codex Cloud environment did not consistently provide the required Python ie-rsi package to fresh tasks.
The package was successfully installed and validated within an active session, but the same dependency was unavailable in subsequent fresh tasks.
Troubleshooting already completed
- Environment configuration and publication diagnostics
- Python package and import validation
- Screenshots and screen recordings of the errors
- Reproduction attempts using desktop Chrome
- Browser network diagnostics supplied privately to OpenAI Support
The problems were reported under Support Case #18041029. Support indicated on November 2, 2026, that the investigation would be transferred to a specialist team. No root-cause determination has been communicated.
Questions for OpenAI engineers and other Codex users
- Are there known issues involving inaccessible Codex task histories after Cloud-build deletion or environment recreation?
- Is saved task history independently recoverable when the execution environment is no longer available?
- What is the expected persistence behavior of published Cloud environment dependencies across fresh tasks?
- Is there a supported recovery procedure that preserves existing task history and environment configuration?
I would appreciate technical guidance or confirmation from anyone who has encountered similar failures.
I am deliberately avoiding further environment recreation until the existing state and recovery options are understood.