On October 7 from 3:15–3:45 PM ET, a backend issue disrupted communication between Dagster+ and customer agents, causing schedule, sensor, and declarative automation ticks to fail with "Unable to reach the user code server" errors, and slowing or timing out code location operations. The incident was fully resolved on October 9 after performance optimizations and fixes were deployed. Failed schedule ticks from the affected window were not automatically retried and may need to be launched manually via the Dagster+ UI.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We've deployed several fixes and performance optimizations that have resolved this issue, and should prevent it in the future.
Between 3:15 PM and 3:45 PM ET (12:15–12:45 PM PT, 19:15–19:45 UTC) on October 7, a backend issue delayed communication between Dagster+ and customer agents. During this window, some schedule, sensor and declarative automation ticks failed with "Unable to reach the user code server" errors, and some code location operations may have been slow or timed out.
The issue was resolved by 3:45 PM ET (12:45 PM PT, 19:45 UTC), and ticks have run normally since. Schedule ticks that failed during this window may not have been retried automatically. If you're missing an expected run from that period, you can launch it manually from the Dagster+ UI.
We're investigating the root cause and will take steps to prevent it from happening again.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with