8 people reported
All time, since Sep 18, including 5 thumbs-up on GitHub.
Account and profile requests fail with status 432 on Windows
“The Codex Windows desktop app is still signed in and recognizes my ChatGPT account, but account/profile-related information fails to load.”
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/16232/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
Signed-in desktop app shows blank profile, subscription and usage details while logs record "Workspace routing is unavailable" for backend endpoints.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
errorMessage="Workspace routing is unavailable"Pasted in 2 reports- Versions
- 26.915.31029
- Platforms
- Windows
- How bad
- Breaks a normal workflow. Some reports say it used to work. Some reports say it blocks them completely.
Part of: Workspace routing account failures4 bugs
- Workspace routing sign-in failure6 people
- Workspace routing startup timeout2 people
- Workspace routing discovery fails2 people
Not quite your bug?
- Repeated login after restart5 people
- Desktop account data 4322 people
- Stuck in Work view7 people
Original reports3, newest first
- [Windows Desktop 26.1007.2314.0] Persistent HTTP 432 workspace routing failures and account lookup failureOn GitHub#52996
- [Windows Desktop 26.915.4065.0] Profile and subscription details blank after update; workspace routing returns 432On GitHub#46786
- [Windows][26.915.31029] Account/profile APIs fail with status 432 "Workspace routing is unavailable"On GitHub#46382