3 people reported
All time, since Oct 8.
Stuck state DB backfill
“After the app quit/crashed (likely during auto-update), every launch showed "Organization settings could not be loaded".”
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/9842/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
App-server startup times out on stuck state DB backfill. Launch shows "Organization settings could not be loaded" because the state db backfill stays in running and app-server waits 30s before failing.
Is this your bug?
File my report- Where
- app-server startup
- Error text
Error: failed to initialize sqlite state runtime under D:\codex-data: timed out waiting for state db backfill at D:\codex-data after 30s (status: running)- Versions
- 0.160.1 to 0.163.0
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it used to work. Some reports say it blocks them completely.
Related: Windows app updates break Codex
Not quite your bug?
- Stuck on startup splash7 people
- Desktop hangs on startup logo7 people
- Stale CODEX_CLI_PATH backend hang2 people
Original reports3, newest first
- Desktop app stuck on "Unable to load organization settings" after update: stale backfill_state=running causes 30s wait = policy-read timeout loopOn GitHub#56389
- [Windows] "Organization settings could not be loaded" caused by state DB backfill stuck in
runningafter crash — app-server times out after 30sOn GitHub#52836 - Windows codex-cli 0.160.1: app-server exits during initialize with SQLite state-runtime/backfill symptomsOn GitHub#52229