Runs for 90 minutes on small-medium size task then tries reconnecting without failure.

Resolved 💬 6 comments Opened Nov 6, 2025 by Rhino1093 Closed Nov 17, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

55.0

What subscription do you have?

Plus

Which model were you using?

codex-medium

What platform is your computer?

_No response_

What issue are you seeing?

no error message. Codex was working for 90 minutes before I stopped it. At the end it was reconnecting, but never made it past attempt 2/5. Prompted it to run on a markdown plan. Finished 50% of phase 1 of the plan. Phase 1 was 8 bullet points about adjusting Data Context foundations in my code.

What steps can reproduce the bug?

Uploaded thread: 019a5705-25f6-7b60-96c5-eb8e988939d0

What is the expected behavior?

_No response_

Additional information

PulseCheckSelectionRefactorPlan.md

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6287
  • #6071
  • #6191
  • #6096
  • #5977

Powered by Codex Action

Rhino1093 · 9 months ago

similar error as #6287

etraut-openai contributor · 9 months ago

Just to confirm, logging out and logging back in doesn't fix it?

Rhino1093 · 9 months ago
Just to confirm, logging out and logging back in doesn't fix it?

I just tried it and it doesnt seem to work on the CLI. It looks like it's trying to proceed with the task but it's definitely not the normal performance. I tried implementing the task with Codex Cloud and it struggled for a bit as well. Had to ask twice for a similar task and Codex Cloud finally pushed through to finishing the task after ~20 minutes. CLI has been 'Reviewing DocumentContext usage' for 3 minutes and its only a 300 line C# file.

etraut-openai contributor · 9 months ago

@Rhino1093, are you still experiencing this problem?

Rhino1093 · 9 months ago
@Rhino1093, are you still experiencing this problem?

I haven’t had this issue since. We can close it and count it as a one off. If it happens to me again I’ll reopen this one or reference it in a new issue. Thanks for following up