Failed tasks which are actually NOT failed

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

What version of Codex is running?

latest (online console via chatgpt.com/codex)

What subscription do you have?

PLUS

Which model were you using?

gpt-5, gpt-5-thinking

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Some of the creative tasks with the biggest workload receive a 'Failed' indicator in the list view of tasks (probably triggered by some timeout). However, when opening the task in a tab, the building/patching process can be still going on with no errors/failures inside the task, with properly fetched logs and healthy pace. (Pics related - see time).

According to my observations, the value of the timeout triggering the 'Failed' indicator is around 60 min.

The task might be in execution for 90-120+ mins and then still succeed, despite being marked as failed in the main view with listed tasks.

<img width="2240" height="853" alt="Image" src="https://github.com/user-attachments/assets/6b2ca49f-032c-413d-992d-7c1ef7217d10" />

<img width="2869" height="1465" alt="Image" src="https://github.com/user-attachments/assets/955eb257-3786-46e6-9907-63e17f45a2ec" />

What steps can reproduce the bug?

The bug appears only for tasks with the biggest expected volume of output token usage.

What is the expected behavior?

The task should remain marked with the dynamic in-progress statuses.

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 9 months ago

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

  • #4991
  • #6296

Powered by Codex Action

etraut-openai contributor · 9 months ago

We had a momentary service outage earlier today that affected codex. The symptom that most codex users experienced was a "Failed" error. I wonder if your task was running during that time. That might explain the symptoms.

Let us know if this is a recurring problem.

RaoG812 · 9 months ago
We had a momentary service outage earlier today that affected codex. The symptom that most codex users experienced was a "Failed" error. I wonder if your task was running during that time. That might explain the symptoms. Let us know if this is a recurring problem.

I think I have been experiencing this repeatedly throughout the past 2 months, might have been related to some outages though.
Overall, I think today was the 6-7th time I have got this.

P.S. It has actually completed the task (not errorless but around 1500 lines of code produced after 3+ hours! Longest run so far!

<img width="763" height="200" alt="Image" src="https://github.com/user-attachments/assets/8b9be9d3-e9b9-401c-baca-48503323de6f" />

etraut-openai contributor · 8 months ago

I think this bug report is stale and no longer relevant. Closing.

alethonymous · 6 months ago

This has happened to me twice today - pretty much exactly on the 60 minute mark it says failed on the tasks list, but then when viewing the failed task its still running.