Dagster: Degraded sensor and schedule evaluations
Dagster+ reported major degradation starting 2026-10-22 20:00 UTC: agent communication problems caused sensor and schedule failures or timeouts and potentially delayed runs. Computed duration was 0 min, though the update describes impact during 20:00–20:24 UTC. Service recovered; failed ticks will resume on their next evaluation, and the root cause remains under investigation.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- resolved
Between 1:00pm and 1:24pm PT (20:00–20:24 UTC), Dagster+ had trouble communicating with agents. During this window, some sensor and schedule evaluations failed or timed out, and some runs may have started late. Service has recovered. Sensors and schedules are evaluating normally, and failed ticks will resume on their next evaluation. We're monitoring and investigating the root cause.
Changes Rewindex caught on this incident
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-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a543582ffdb770ea…
Impact, status and times are the vendor’s own, as last archived. View on dagstercloud.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Dagster, started 2026-10-22 20:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded sensor and schedule evaluations
- Vendor
- Dagster
- Date
- URL
- https://rewindex.com/company/dagster/incidents/qxcg5q1zjp0k
Dagster profileRecent Dagster incidentsAll outages on October 22, 2026Dagster in October 2026MarkdownJSON