US - Orchestrator - Intermittent errors and degraded performance in Orchestrator

Final update

## Customer impact Between approximately 13:00 UTC and 18:15 UTC on October 7, 2026, customers in the US region experienced intermittent errors and slow responses in Orchestrator. Affected users may have seen Orchestrator pages fail to load, for example the Jobs page returning “An error has occurred,” and robot operations such as queue transactions and session starts may have intermittently timed out. Other UiPath services that depend on Orchestrator may also have seen slower responses or errors during this period. ## Root cause Several frequently-used Orchestrator operations each relied on a shared short-lived resource inside the database, including the routine status check that every running robot performs. As the volume of concurrent robot activity in this region grew, requests began queueing for access to that shared resource instead of completing their work. The effect was selective rather than a general slowdown: the operations that used this resource were delayed, while others continued to run normally. Because the database’s processor, memory and storage usage all remained within normal ranges, routine capacity monitoring did not indicate a problem. ## Detection Our automa

1. Postmortem · Oct 14, 11:42 UTC
   ## Customer impact Between approximately 13:00 UTC and 18:15 UTC on October 7, 2026, customers in the US region experienced intermittent errors and slow responses in Orchestrator. Affected users may have seen Orchestrator pages fail to load, for example the Jobs page returning “An error has occurred,” and robot operations such as queue transactions and session starts may have intermittently timed out. Other UiPath services that depend on Orchestrator may also have seen slower responses or errors during this period. ## Root cause Several frequently-used Orchestrator operations each relied on a shared short-lived resource inside the database, including the routine status check that every running robot performs. As the volume of concurrent robot activity in this region grew, requests began queueing for access to that shared resource instead of completing their work. The effect was selective rather than a general slowdown: the operations that used this resource were delayed, while others continued to run normally. Because the database’s processor, memory and storage usage all remained within normal ranges, routine capacity monitoring did not indicate a problem. ## Detection Our automated monitoring detected the degradation within approximately 35 minutes of customer impact beginning, and our engineers identified the underlying contention during the event. Because this was a contention problem rather than a shortage of capacity, and all capacity indicators were normal, increasing
2. Resolved · Oct 7, 19:06 UTC
   We have the issue in the East US region and error rates and latency returned to normal levels.
3. Monitoring · Oct 7, 18:13 UTC
   We have applied a capacity increase to the affected database infrastructure in the East US region and error rates and latency returned to normal levels. We will provide an update as soon as more information is available.
4. Investigating · Oct 7, 17:37 UTC
   We are investigating reports of intermittent slowness and errors affecting a subset of organizations in the East US region of Automation Cloud. Affected users may see pages in the Orchestrator UI fail to load (for example, the Jobs page returning "An error has occurred"), and robot operations such as queue transactions and session starts may intermittently time out. We will provide an update as soon as more information is available.