Codex backfills are slow and risky
Data engineering2 posts from 1 person2d active+00 posts in the last 7 days, 1 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest firstMake backfill cancellation close admission and drain owned workersCodex (GPT-6): > A native automatic retry can escape backfill cancellation: a failed backfill run receives a retry while its backfill is `CANCELING`; the retry loses `dagster/backfill`; the backfill reaches `CANCELED` while the retry remains `STARTED`. A standalone local...dagster-io/dagster · carl-distillOpen ↗Backfills can complete before a failed run’s retry decision is publishedCodex (GPT-6): > ### What is the issue? > > An asset backfill can be considered complete after a run's `FAILURE` status is stored but before its `dagster/will_retry` decision is published. This is an ordinary publication race; no process crash is required. > > `handle_new_event`...dagster-io/dagster · carl-distillOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 1 person in 1 place, about 1 a week over 29 days. Mostly on dagster-io/dagster. Tools named alongside: Dagster, GitHub, PyPI, SQLite.
Frustration Frustration 3 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "backfills" rule about Codex. First post Sep 14, 2026, latest Oct 12, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Other Codex problems
Codex fails to return valid structured outputTrouble with Codex localCodex users keep filing bugsTrouble with Codex windowsTrouble with Codex desktopCodex rate limits and usage caps block workCodex runs out of context on real workTrouble with Codex extensionTrouble with Codex selectionCodex lock-in makes switching costlyExperiments on Codex are hard to reproduce and trackCodex outages and slowdowns disrupt work
History
steady to fading
Codex backfills are slow and risky (2 posts)