Changes / Dagster / Some Dagster Plus Serverless Runs Failing to Start

Dagster: Major incident: Some Dagster Plus Serverless Runs Failing to Start

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 99%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Some Dagster Plus Serverless Runs Failing to Start
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2024-05-14 18:53 UTC
AddedResolved time#5
Before: not present
After: 2024-05-14 20:16 UTC
AddedAffected components#6
Before: not present
After: API
AddedUpdateinvestigating#7
Before: not present
After: Some Dagster Plus Serverless runs are failing to start with an "Agent detected that run worker failed." error. We are working with our cloud provider to investigate the root cause of the problem as well as adding automatic retries for the underlying error that is causing the runs to fail to start.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate the root cause of this issue with our cloud provider. We are rolling out a change to add additional automatic retries to runs that are affected by this issue.
AddedUpdateidentified#9
Before: not present
After: Our cloud provider has identified the root cause of the problem and is in the process of rolling back the change that caused it. We'll continue to provide updates as we work to resolve the issue.
AddedUpdateresolved#10
Before: not present
After: The fix for this problem is now live.

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

History of this incident

When (UTC)ChangeKind
Major incident: Some Dagster Plus Serverless Runs Failing to Start (this change)Major incident

All Dagster changes → · Dagster profile · Markdown · JSON