Changes / Dagster / Issues with global op concurrency keys

Dagster: Major incident: Issues with global op concurrency keys

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: degradation (model (Jev), 37%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Issues with global op concurrency keys
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-02-07 15:37 UTC
AddedResolved time#5
Before: not present
After: 2025-02-07 16:11 UTC
AddedAffected components#6
Before: not present
After: API, Dagster Cloud UI
AddedUpdateidentified#7
Before: not present
After: 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.
AddedUpdatemonitoring#8
Before: not present
After: 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.
AddedUpdateresolved#9
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Issues with global op concurrency keys (this change)Major incident

All Dagster changes → · Dagster profile · Markdown · JSON