Skip to content

Failed tasks which are actually NOT failed #6303

@RaoG812

Description

@RaoG812

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.

Image Image

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcodex-webIssues related to Codex Web

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions