UiPath Status

Postmortem: ## Customer impact

Between July 20, 2026 at 4:28 pm UTC and 7:32 pm UTC, a subset of customers experienced degraded Orchestrator Jobs performance in the U.S. region, with delays in job processing during that window.

Root cause

The incident was triggered by a routine product deployment to Orchestrator that included a schema change to an existing column on a core Orchestrator database table. Specifically, a change to the column's size. The large size of the Jobs table made this schema change operation significantly more resource-intensive and longer-running than anticipated, causing it to still be in progress once normal U.S. traffic picked up, an overlap that had not been anticipated. The combination of the ongoing schema change and concurrent production traffic generated increased database load, which caused latency and delays in job processing. As the change rolled out, the affected databases were impacted progressively rather than all at once.

The script had been reviewed and tested prior to rollout. However, the resource impact observed here did not reproduce during pre-deployment testing, as it depended on production-scale traffic conditions that were not present in the test environment.

Detection

Our automated monitoring identified the issue at 4:28 pm UTC on July 20, 2026, and the alert was acknowledged immediately. As the extent of the customer impact became clear, the incident was formally declared customer-impacting at 7:12 pm UTC.

Response

As the schema change progressed, the resulting database load increased progressively across the affected databases rather than all at once. The team mitigated the issue in two stages: a first round of database capacity increases around 5:00–5:30 pm UTC addressed the databases affected at that point, and as impact continued to build on the remaining databases, a second round of capacity increases around 7:00–7:30 pm UTC was applied, fully resolving the elevated load.

At 7:19 pm UTC, a public status update confirmed the cause had been identified: degraded performance affecting Orchestrator Jobs in the U.S. region, with users potentially seeing delays when executing jobs. Mitigation actions were already under way at that point.

The database schema change script was stopped, and database capacity was increased as a mitigation measure. During the response call, the engineering team monitored database utilization, which was observed dropping and then stabilizing. By the end of the call, all databases were underutilized and the issue was confirmed mitigated. At 7:32 pm UTC, the incident was marked resolved, and the public status page confirmed that Orchestrator performance had returned to expected levels

Follow-up

Several actions will be taken following this incident:

• We are building a safer, more automated process for running database schema changes that reliably schedules resource-intensive changes outside of peak traffic hours, rather than relying on manual timing.
• We are extending our monitoring systems to more accurately include customer-visible slowdowns in parts of the platform that rely on Orchestrator (Maestro, Agents).

Resolved: The issue has been resolved and Orchestratorperformance has returned to expected levels after degraded performance impacted jobs in US. Impact: No ongoing user impact.

Identified: The issue causing degraded performance impacting Jobs for Orchestrator in US has been identified, and corrective actions are underway. Impact: Users may continue to see delays when executing jobs. We will provide further updates as mitigation progresses.

Identified: We have identified the cause of the degraded performance impacting [impacted functionality / user symptom] for [Service] in [Region] and are working on mitigation. Impact: Users may experience [describe ongoing impact, if any]. Additional updates will be provided as we move toward resolution.

Resolved: The mitigation has been effective, and all affected services are now operating normally. Service health is stable, and error rates have returned to expected levels. We apologize for the disruption and appreciate your patience throughout this incident.

Monitoring: Our engineering team has applied a mitigation to address the issue. Since implementing the mitigation, we have observed a significant reduction in errors, and the affected service is returning to a stable state. We are continuing to closely monitor the service to ensure stability and will provide further updates.

Investigating: We are investigating degraded performance affecting Document Understanding Helix 2.0. The extractor and splitter/classifier are experiencing increased delay and occasional failed requests in the Europe region

Investigating: We are investigating degraded performance impacting Document Understanding Service in Europe Region. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: Our mitigation efforts are completed and impacted services are fully stable now. We will post a detailed summary of incident soon.

Identified: We are continuing mitigation activities and the impacted regions are showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We have identified impact in the US Delayed environment as well, and are continuing mitigation activities.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Investigating: We are still investigating the reports of delayed ingestion of robot logs. Our teams are working to identify the cause and will share more details as the investigation progresses.

Monitoring: Mitigation has been applied. We are monitoring closely to ensure stability.

Investigating: We are investigating reports of missing robot logs in the US region.

Our teams are working to identify the cause and will share more details as the investigation progresses.

Investigating: We are investigating reports of missing robot logs in the US region. Our teams are working to identify the cause and will share more details as the investigation progresses.