4 people reported
All time, since Oct 4.
Desktop requests expire queued after RPC stalls fill in-flight slots
“Codex Desktop intermittently reaches a persistent state where Send shows an error icon, Retry also fails, and fully restarting the app restores messaging.”
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/19031/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
Send and Retry fail with "App server request expired while queued", the model picker and new chats stall, and only a full restart restores messaging.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
errorMessage="App server request expired while queued"- Versions
- 0.162.0 to 0.163.0
- Platforms
- Windows
Related: Conversation writer lock blocks continuing
Not quite your bug?
- CLOSE_WAIT socket leak3 people
- Active writer conflict4 people
- Stream disconnects mid-response7 people
Original reports4, newest first
- [Windows Desktop] App-server request scheduler permanently saturates in-flight slots after RPC stalls/bursts, expiring all queued requestsOn GitHub#56673
- Multiple chats cause global request blocking in the Windows desktop appOn GitHub#56118
- Windows Desktop global Send stalls with a full client scheduler; need supported request lifecycle diagnosticsOn GitHub#54969
- [Windows Desktop 26.930] Sent read timeouts retain all 8 host RPC slots; Send/Retry fails until restartOn GitHub#50812