2 people reported
All time, since Sep 14.
Thread history projection stalls
“Read-only diagnostics confirm later events remain in the durable rollout, but history projection is stuck at a duplicate ordinal.”
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/16484/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
Thread history projection stalls after duplicated rollout ordinal. Rollout keeps growing, but thread/items/list and thread/turns/list keep returning the state as of the duplicate.
Is this your bug?
File my report- Where
- app-server
- Error text
thread history projection for <thread> expected ordinal 5126, got 5125- Versions
- 0.153.4
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Part of: Thread history missing or unopenable12 bugs
- Threads fail to open3 people
- Response vanishes after streaming3 people
- Older turns missing from history3 people
- Completed turns return empty items3 people
- Chat replies go blank after switching4 people
- Remote chat history missing2 people
- Final answers not displayed3 people
- read_thread returns only content-reference placeholders for ChatGPT assistant replies8 people
- Thread history rolls back2 people
- Task transcript goes blank2 people
Show all 11Show only the largest 10
- Chats fail to open2 people
Original reports2, newest first
- app-server: thread history projection stalls forever after a duplicated rollout ordinal ("expected N, got N-1"); thread/items/list and thread/turns/list stop reflecting new turnsOn GitHub#46316
- [Windows Codex App] Task repeatedly returns to stale history: duplicate ordinal blocks projectionOn GitHub#45473