UiPath incident
Delays starting jobs on Cloud Robots in the US region
UiPath experienced a minor incident on October 2, 2026 affecting Orchestrator and Orchestrator and 1 more component, lasting 39m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 02, 2026, 04:23 PM UTC
Since about 15:05 UTC, some customers in the US region may see jobs that run on Cloud Robots take longer than usual to start, or stay in the Pending state. Jobs on your own robots are not affected, and neither are other regions. We've found the likely cause and are working to restore normal job processing. Jobs that are already queued are not lost and will be processed once the issue is resolved. We'll post another update within 60 minutes.
- monitoring Oct 02, 2026, 04:34 PM UTC
We've applied a fix for the issue that delayed jobs on Cloud Robots in the US region, and jobs are starting normally again. Jobs that were delayed are now being processed. We're monitoring to make sure the service stays stable and will post another update within 60 minutes.
- monitoring Oct 02, 2026, 04:51 PM UTC
After further work on the issue, jobs on Cloud Robots in the US region are now starting normally. Jobs that were delayed earlier are being processed. We're continuing to monitor the service and will post another update once the issue is resolved.
- resolved Oct 02, 2026, 05:03 PM UTC
This issue has been resolved. Between 15:05 and 16:39 UTC, jobs on Cloud Robots in the US region were slow to start or stayed in the Pending state. Jobs have been starting normally since 16:39 UTC, and jobs that were delayed during this time have now been processed. We apologize for the disruption.