Dagster: Scheduling runs and sensors delay
Timeline of updates
- resolved
A configuration change caused an delay in scheduling runs and sensors. We identified and fixed the issue. The issue was identified at 12:15pm PST and was resolved at 1:30pm PST.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fe71f8b7621f43c1…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Dagster, started 2026-02-24 00:33 UTC, resolved after 0 min, 1 update(s).
- Title
- Scheduling runs and sensors delay
- Vendor
- Dagster
- Date
- URL
- https://rewindex.com/company/dagster/incidents/g0mpp9jkk9j8
Dagster profileRecent Dagster incidentsAll outages on February 24, 2026Dagster in February 2026MarkdownJSON