1 person reported
All time, since Oct 14.
Task turn fails with UNAVAILABLE
“A subsequent read showed the previous turn and no new turn from the failed request.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/12783/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Continuing an existing task fails with UNAVAILABLE error. Codex Tasks connector can list and read the task, but continuing it fails and no new turn appears.
Is this your bug?
File my report- Where
- Codex Tasks connector
- Error text
Codex Tasks could not complete the request.- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Dot cloud task create and continue fail with UNKNOWN18 people
- Dot cannot read local threads57 people
- Dot tasks missing browser tools10 people