UiPath incident
Orchestrator: API trigger jobs are ignoring settings, configured under Execution Target(account, machine, hostname)
UiPath experienced a minor incident on July 3, 2026 affecting Orchestrator and Orchestrator and 1 more component, lasting 7h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 03, 2026, 02:24 AM UTC
We have identified the issue and currently working on a fix.
- identified Jul 03, 2026, 03:28 AM UTC
We have identified the cause of the degraded performance impacting Orchestrator API trigger jobs in US and we are working on mitigation.
- identified Jul 03, 2026, 03:47 AM UTC
We are continuing to work on a fix for this issue.
- identified Jul 03, 2026, 05:09 AM UTC
The fix is now live in the US and Japan. The team is currently focused on mitigating the issue in the remaining environments
- identified Jul 03, 2026, 06:11 AM UTC
The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.
- identified Jul 03, 2026, 07:22 AM UTC
Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.
- identified Jul 03, 2026, 08:27 AM UTC
Services have been restored to operational status in the EU, Australia, and Switzerland. Validation for the remaining regions is underway.
- identified Jul 03, 2026, 08:44 AM UTC
Services have been restored to operational status in the India, UAE, Canada, EU, Australia, and Switzerland. Validation for the remaining regions (UK, Singapore) is underway.
- identified Jul 03, 2026, 09:54 AM UTC
The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland
- monitoring Jul 03, 2026, 10:05 AM UTC
Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.
- resolved Jul 03, 2026, 10:33 AM UTC
This incident has been resolved.
- postmortem Jul 16, 2026, 09:37 AM UTC
## Customer impact Between **July 3, 2026 at 02:19 UTC** and **July 3, 2026 at 10:00 UTC**, a subset of customers experienced incorrect execution behavior for **Orchestrator API trigger jobs**. Jobs initiated through API triggers did not consistently use their configured execution target, including the intended template, account, and machine settings. The issue affected customers in the **U.S. and Japan regions**. Once identified, the fix was deployed to those regions first and then rolled out to the remaining affected regions. Service was fully restored after deployment was completed across all environments. ## Root cause The incident was caused by a recent change to Orchestrator’s job allocation logic that unintentionally altered how execution targets were resolved for API-triggered jobs. As a result, API-triggered jobs did not consistently honor their configured template, account, and machine settings, and could instead be allocated to other eligible machines and accounts within the same folder. ## Detection The issue was first identified through a customer report on **July 3, 2026 at 02:19 UTC**. The incident was acknowledged immediately, and engineering quickly confirmed the underlying issue. A public status page update was published at **02:24 UTC** to inform customers that the issue had been identified and that remediation was in progress. ## Response Following the customer report, engineering initiated an incident response and began mitigating the issue by reverting the affected environments to the previous stable version while simultaneously preparing a permanent fix. After the corrective changes were developed, reviewed, and validated, they were deployed first to the U.S. and Japan regions, where service was confirmed to be operating normally. The deployment was then completed across the remaining affected regions. Following validation that API-triggered jobs were once again honoring their configured execution targets, the incident was marked mitigated and subsequently resolved. ## **Follow-Up** **Completed** * Added automated regression tests to verify that API-triggered jobs consistently preserve and honor their configured execution targets, including template, account, and machine settings.