Companies / Dagster / incidents
Dagster: Issues with global op concurrency keys
Dagster reported a major API and Dagster Cloud UI degradation from 2025-02-07 15:37 UTC to 2025-02-07 16:11 UTC (34 min): some runs with concurrency keys lacking explicit configuration or a default limit were blocked, and concurrency settings had UI issues. Fixes restored progress, but previously blocked runs might still require manual termination.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: APIDagster Cloud UI
Timeline of updates
- identified
Some runs containing ops tagged with concurrency keys that have not been configured explicitly or with a default limit are getting blocked. Separately, there are some UI issues affecting the concurrency key settings page. We have identified fixes for these and are in the process of rolling them out.
- monitoring
The fixes has been rolled out and previously blocked runs appear to be progressing. We are continuing to monitor for any issues. The previous blocked runs should progress with their step execution, but may not reach a terminal state and may need to be manually terminated.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Issues with global op concurrency keys 2025-02-07 15:37 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Dagster profile · Recent Dagster incidents · Markdown · JSON