Problemsby GlyphDagster backfills are slow and risky
4 posts from 4 people4d activeFading, +0 this week
Posts per day
The posts behind it
[BUG] Intermittent gRPC DecodeError on ExternalJobReply fails code location reload, so backfill fails
...deserialization. ### How to reproduce? This is intermitten according to what i observe hard to reproduce. What i think in production: What i simulated: I used a monitor repeated the daemon's ExternalJob call against the production code server: 45 jobs every 10 seconds with 4...
MultiPartitionsDefinition + multi_run backfill_policy: job-page backfills collapse every run to the first partition
...wrong data for every run after the first, with no error and a "Success" status. ## Workaround Set `max_partitions_per_run=1` on the asset's `BackfillPolicy`. This routes `submit_backfill_runs` through its other branch (plain partition-name strings instead of...
Asset backfill marks partitions skipped via `output_required=False` as failed (1.13.22+)
### What's the issue? Since 1.13.22, when every run of an asset backfill has finished and some targeted partitions have no materialization, `_backfill_is_stalled` in `dagster/_core/execution/asset_backfill.py` marks those partitions and everything downstream of them as failed,...
Partitioned jobs with automation_condition fail during subsetting and execute_in_process without explicit config
...Dagster 1.13.19. It requires no external resources, sensors, or running daemon. Both failing calls were verified independently. ### Dagster version 1.13.19 ### Deployment type Local ### Deployment details Dagster OSS on Linux, Python 3.13.15. ### Additional information The...
Companies and products named
About this problem
Evidence
4 posts from 4 people in 1 place, about 1 a week over 32 days. Mostly on dagster-io/dagster. Tools named alongside: Docker, PostgreSQL, AWS.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "backfills" rule about Dagster. First post Sep 21, 2026, latest Oct 22, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
The same problem elsewhere
Backfills are slow, costly and risky
10 posts from 10 people on GitHub issues, Reddit.
Apache Airflow backfills are slow and risky
4 posts from 4 people on GitHub issues.
PostgreSQL backfills are slow and risky
3 posts from 3 people on GitHub issues.
Codex backfills are slow and risky
2 posts from 1 person on GitHub issues. Unverified.
MLflow backfills are slow and risky
2 posts from 2 people on GitHub issues. Unverified.
Claude backfills are slow and risky
2 posts from 2 people on GitHub issues. Unverified.
Other Dagster problems
Dagster users keep filing bugs
Top post: "Allow customizing the content/layout of Dagster+ alert notification message", one of 6 posts from 6 people on GitHub issues.
Trouble with Dagster asset
Top post: "Asset daemon: `execution_failed()` on unpartitioned assets issues one un-batched query per asset per tick", one of 3 posts from 3 people on GitHub issues.
History