Codex Stuck Sessions & Resume Errors

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.

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: timeout or missing queued message

  Save the prompt and read the full error suffix, then check whether your message is already in the conversation or queue before resending.

  Desktop app · macOS

• Codex resume failed: cannot reopen a session

  Check whether the failure began right after a Codex client update, since one reported resume failure followed an update.

  Codex CLI, Desktop app, IDE extension · Windows, macOS

• Codex session stuck: not producing output (context / compaction)

  Watch for a 'Compacting context' status line with an elapsed timer before deciding the turn has hung.

  Codex CLI, Desktop app, IDE extension · Windows, macOS

• Codex error creating task: timeout — checks before you reset

  Save your unsent prompt, check whether a task was created anyway, then compare new-task creation with an existing conversation.

  Desktop app · Windows, macOS

Reached a usage limit instead? Check Codex usage limits and reset times.