UiPath incident
Multiple Regions - Studio Web & Solutions Mgmt - Resource Configuration Screen Not Loading
UiPath experienced a major incident on August 18, 2026 affecting Studio Web and Solutions Management and 1 more component, lasting 6h 56m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 18, 2026, 12:08 PM UTC
We have identified the root cause of an issue in Studio Web where the resource configuration screen for changing resource attributes is not loading. We are deploying a fix.
- identified Aug 18, 2026, 01:05 PM UTC
Deployment of the fix is in progress. We will provide further updates as the deployment progresses.
- identified Aug 18, 2026, 02:06 PM UTC
The fix has been verified and is being rolled out across all remaining regions. We are monitoring the deployment and recovery. Thanknyou for your patience.
- identified Aug 18, 2026, 03:06 PM UTC
The rollout is progressing as expected across the remaining regions. We continue to monitor the deployment. Thank you for your patience.
- identified Aug 18, 2026, 05:03 PM UTC
The rollout is progressing as expected across the remaining regions. We continue to monitor the deployment. Thank you for your patience.
- monitoring Aug 18, 2026, 06:12 PM UTC
The rollout is progressing as expected across the remaining regions. We continue to monitor the deployment. Thank you for your patience.
- resolved Aug 18, 2026, 07:05 PM UTC
The rollout is completed and the issue should be resolved.
- postmortem Sep 16, 2026, 08:16 AM UTC
## Customer impact Between August 14, 2026 and August 18, 2026 at 7:05 pm UTC, the resource configuration screen in Studio Web did not load. Customers could not view or change resource attributes for process resources within the Solutions Management area of Studio Web. Overall, the impact lasted almost a week. Other Studio Web capabilities were not identified as affected. ## Root cause An incorrect resource configuration package version was included in a Studio Web release. Studio Web loads this package to display resource configuration details; because the release referenced the wrong version, the resource configuration screen failed to load. The mismatch was produced by the frontend framework version upgrade for the two services. The fix reverted the package version to the previous working version and required an expedited Studio Web deployment. ## Detection The issue was detected at 11:42 am UTC on August 18, 2026 based on manual smoke testing. The incident was declared customer-impacting at 11:43 am UTC. ## Response At 11:49 am UTC, an expedited fix deployment was started for Studio Web. By 12:08 pm UTC, the root cause had been identified, and a public status update confirmed that a fix was being deployed for the resource configuration screen. At 1:41 pm UTC, the fix was deployed to the first environment. At 1:43 pm UTC, the issue was confirmed resolved in that environment, and deployment continued to remaining regions. By 2:06 pm UTC, the fix had been verified and was being rolled out across all remaining regions. At 6:12 pm UTC, the incident was marked mitigated while deployment monitoring continued. At 7:05 pm UTC, the rollout completed and the incident was marked resolved. ## Follow up 1. Add documentation and protocols for frontend framework version upgrade 2. Add specific automated tests to prevent such regressions on resource configuration