#Couldn't start fix task using codex code review
1 messages · Page 1 of 1 (latest)
Hi @runic basalt. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
This specific “Couldn’t start fix task” error message is not described in the provided knowledge sources, so I can’t say exactly why it’s happening in your case.
From the available Codex-related issues, there are a few patterns worth checking:
-
Check OpenAI status page
Recent Codex outages have caused generic failures when starting or running Codex tasks, which were later confirmed and resolved via the status page. [Codex error rate; GitHub auth incident]
It’s worth checking the status page around the time you see the error. -
GitHub connector / permissions issues
Several users have seen Codex fail to operate on PRs or repos due to GitHub connector/auth problems (e.g., “You don’t have the ability to clone this repository”, code reviews not running, or quota/credit errors). In many cases, disconnecting and reconnecting the GitHub connector in ChatGPT settings helped, sometimes for each user in the org. [Unable to clone repo; Usage limits bug]- Go to
chatgpt.com/codex/settings/connectors - Unlink GitHub
- Re-link GitHub and re‑authorize access to the repo/organization
- Retry the fix task
- Go to
-
Quota / credits issues
There have been cases where Codex reported that usage limits were reached even though the UI showed quota remaining; reconnecting GitHub for each user resolved it. [Usage limits bug; Codex rate card]
If you’re on a business/enterprise workspace, ask an admin to:- Confirm Codex credits are available
- Try disconnecting/reconnecting GitHub from their account as well
-
General Codex instability
There were recent periods where Codex couldn’t create new tasks at all, which was later fixed. [Codex cannot be used; Failing to create tasks]
If this is a transient backend issue, it may resolve after some time; checking the status page is the best way to confirm.
Because the knowledge sources don’t document this exact error string or a definitive fix, if the above steps don’t help your best next step is to contact OpenAI support with:
- A screenshot of the error
- The workspace name
- The repo/PR URL (or a redacted example)
- Approximate time (with timezone) when you tried to start the fix task
That will let support correlate your issue with any backend or connector problems.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@runic basalt Kapa.ai is still learning and improving, please let me know how I did by reacting below.
quota is green, connector to github is working. I use it in other tasks.
screenshot of the error? why, its the text I send onyl, no more information
workspace name = what do you mean? dont found workspace in codex, enviroments only