UiPath experienced a major incident on August 24, 2026 affecting Apps and Apps and 1 more component, lasting 1h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 24, 2026, 10:43 AM UTC
We have identified the cause of an issue impacting a small number of customers using UiPath Apps authored from the Studio Web service across multiple regions. Our teams are ready with a fix, and deployment is about to begin across the affected regions. We will continue to monitor the deployment and provide further updates as the fix takes effect.
- monitoring Aug 24, 2026, 11:30 AM UTC
The fix has been successfully deployed across all affected regions, and the issue has been mitigated. We are closely monitoring the service to ensure the fix continues to perform as expected and will provide further updates as needed.
- resolved Aug 24, 2026, 11:55 AM UTC
The issue has been resolved, and the service is operating as expected. No further impact has been observed.
- postmortem Sep 01, 2026, 11:47 AM UTC
## Customer impact Between August 19, 2026 at 2:33 pm UTC and August 24, 2026 at 11:30 am UTC, a subset of customers could not load UiPath Apps projects authored from Studio Web. Affected customers experienced complete unavailability of Apps projects rather than slowness or degraded performance. The impact was limited to a small set of customers, whose Apps service was hosted in the Japan region. The total customer-impacting duration was approximately 4 days and 21 hours. ## Root cause The root cause was a deployment mismatch between Studio Web and UiPath Apps. On August 19, 2026, Studio Web received a scheduled update in the EU region that included a framework upgrade. The corresponding UiPath Apps update containing the framework upgrade had not yet been deployed to Japan scale unit. An earlier Apps update that was already compatible with the new framework version had been deployed to all regions except Japan, where deployment had been deferred due to unrelated reasons. As a result, the Japan region was still running an older Apps version that was not compatible with the updated Studio Web. ## Detection The issue was reported by a customer through their UiPath account team on August 24, 2026 at 9:36 am UTC. An incident was opened at 10:21 am UTC, and a public status page incident was declared within a minute. Existing automated monitoring did not detect the issue because it validates matched deployment combinations; improving detection for mixed configurations is part of our follow-up plan. ## Response Within minutes of opening the incident, we identified the deployment mismatch as the root cause and decided to accelerate deployment of the corresponding UiPath Apps update to all affected regions, aligning Apps with the Studio Web version already being served to impacted customers. At 10:43 am UTC, we posted a public status update confirming the cause had been identified and that the fix was being deployed. At 10:52 am UTC, deployment was in progress for the remaining regions, with several regions already complete. At 11:30 am UTC, we confirmed the fix had been deployed across all affected regions and marked the incident mitigated. At 11:55 am UTC, after monitoring showed no further impact, the incident was marked resolved. ## Follow up 1. Add automated alerting on production telemetry to detect Apps load failures correlated with the Studio Web version being served. 2. Implement synthetic monitoring that regularly loads an Apps project authored from Studio Web across representative customer configurations and alerts on failure. 3. Adjust release sequencing for tightly coupled Studio Web and Apps changes so that dependent Apps updates are fully deployed to all regions before the newer Studio Web experience reaches customer traffic.