Problemsby GlyphDagster users keep filing bugs
6 posts from 6 people5d activeFading, +0 this week
Posts per day
The posts behind it
Multipartition pagination can return malformed keys from dynamic dimensions
### Describe the bug A `MultiPartitionsDefinition` can include a named `DynamicPartitionsDefinition`, but dynamic partition keys are not validated against the multipartition delimiter (`|`). The normal `get_partition_keys()` path filters generated keys with...
Can't see logs while using AzureBlobComputeLogManager without prefix
...leads to an error "No log file available". The root analysis shows, that there is a problem with a blob-key-mismatch. The dagster webserver uses: - Correct account and container. - An empty prefix, generating /storage/.../grdhkaxa.err. - Azure returns the blob name as...
[dagster-slack] slack_on_failure / slack_on_success hooks fail with slack_resource: 'WebClient' object has no attribute 'get_client'
### What's the issue? Since 1.10.18 (#30112), the built-in `slack_on_failure` and `slack_on_success` hooks call `context.resources.slack.get_client()`. That works for `SlackResource`, but the function-style `slack_resource` (still exported and documented) provides a...
Add "Error Message" column to the Runs UI page
**What's the use case?** When monitoring pipeline runs in the Dagster UI, users currently need to click into each individual failed run to understand why it failed. This is time-consuming, especially when managing many runs at once. Having a short error message (1 sentence or a...
Allow customizing the content/layout of Dagster+ alert notification message
...Dagster+ alert policies (we use Slack) currently render a fixed message template with no way to control which fields are shown or how they're prioritized. The only content-related option exposed today is policy_options.include_description_in_notification. For teams routing...
A force-terminated run (MARK_AS_CANCELED_IMMEDIATELY) later moves CANCELED -> SUCCESS when its worker finishes
### What's the issue? A run force-terminated with `MARK_AS_CANCELED_IMMEDIATELY` reads CANCELED, but its run worker is not stopped (as documented). When the worker's steps later finish, it emits `STEP_SUCCESS` and `RUN_SUCCESS`, the event log accepts them, and the run's status...
Companies and products named
About this problem
Evidence
6 posts from 6 people in 1 place, about 1 a week over 58 days. Mostly on dagster-io/dagster. Tools named alongside: Slack, PostgreSQL, Docker, Microsoft Azure.
Frustration Frustration 1 of 3· Seen on GitHub issues
How it was grouped
Posts about Dagster that state a pain but match no known issue yet. First post Sep 5, 2026, latest Nov 1, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Dagster problems
Dagster backfills are slow and risky
4 posts from 4 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