Codex RescueCodex troubleshooting
Codex stuck sessions & resume errors
Troubleshoot stuck Codex turns, stalled sessions and resume failures. Check session state and recovery options before starting over or removing data.
When Codex appears stuck, preserve the useful work before trying recovery steps. A stalled turn and a session that cannot resume are different problems; choose the guide that matches what you can still see and control.
A session can be slow, waiting for a tool, stuck in one turn or unable to resume an earlier chat. Those are not identical failures. Record the last visible action, whether there is new output, and whether you can still access the current conversation. Preserve useful work before testing recovery: a new chat may be a helpful comparison, but it should not replace the only copy of a task or local project state. Check public status when several clients fail at the same time, while keeping local symptoms in view.
The guides below distinguish a stalled current turn from a resume failure and related session messages. Use the one that matches what you can actually observe. Avoid deleting session files or the entire Codex home as a generic reset. If the current task remains accessible, keep it while gathering a redacted error line, client version, operating system and time of failure. That evidence is more useful than a broad “stuck” label when deciding whether to wait, retry a specific action or report a reproducible bug.
What to check first
- Save relevant output and note the last completed action.
- Determine whether the current turn is stalled or an old session will not reopen.
- Use targeted recovery steps before deleting local session files.
Sessions troubleshooting guides
Codex error submitting message: what to check
Save the prompt and read the full error suffix, then check whether your message is already in the conversation or queue before resending.
Codex model at capacity: what to check
Check OpenAI's current status and record the exact error, time, model and client before retrying once.
Codex model metadata not found: what to check
Check whether a short request actually succeeds, then record the warning and exact model identifier.
Codex model not supported: account check
Record the exact model name and client, then check whether that model is available to your account and workspace.
Codex resume failed: recover your next steps
Check whether the failure began right after a Codex client update, since one reported resume failure followed an update.
Codex session stuck or compacting: what to do
Save your work, then check for pending approvals, tool activity and repeated compaction before starting another turn.
Codex task creation timeout: fix
Save your unsent prompt, check whether a task was created anyway, then compare new-task creation with an existing conversation.
Back to all Codex error messages →
Reached a usage limit instead? Check Codex usage limits and reset times.