Multiple Regions - UiPath Apps - Partial Outage
Final update
## 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 Augu
Timeline
- Postmortem · Sep 1, 11:47 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
- Resolved · Aug 24, 11:55 UTC
The issue has been resolved, and the service is operating as expected. No further impact has been observed.
- Monitoring · Aug 24, 11:30 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.
- Identified · Aug 24, 10:43 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.