UiPath experienced a major incident on August 25, 2026 affecting Solutions Management, lasting 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 25, 2026, 09:41 AM UTC
We have identified an issue affecting the Solution Deployment feature in Studio Web in the Japan region, where solution deployments may fail. A fix has been prepared and will be rolled out shortly. We will provide further updates as more information becomes available.
- monitoring Aug 25, 2026, 09:47 AM UTC
The fix has been successfully deployed in the Japan region, and the issue has been mitigated. We are closely monitoring the service to ensure Solution Deployment continues to operate as expected and will provide further updates as needed.
- resolved Aug 25, 2026, 10:12 AM UTC
The issue has been resolved, and Solution Deployment in Studio Web is operating as expected in the Japan region. No further impact has been observed.
- postmortem Sep 16, 2026, 08:19 AM UTC
## Customer impact Between August 25, 2026 at 9:30 am UTC and August 25, 2026 at 10:13 am UTC, Solution Deployment in Studio Web was unavailable for customers in the Japan region. Affected customers could open Studio Web but were unable to use the deploy feature. The entire Japan region was affected. The incident lasted 42 minutes. Service mitigation was confirmed at August 25, 2026 at 9:47 am UTC, and full resolution was confirmed at August 25, 2026 at 10:13 am UTC after monitoring showed no further impact. ## Root cause A required deployment update for the Solution Deployment service had not been applied to the Japan region, leaving it on an outdated version. This prevented the deploy feature in Studio Web from operating correctly for customers in that region. ## Detection The issue was first detected by a customer on august 25, 2026 at 9:30 AM UTC. The customer raised a support issue, and an incident was then created from it. ## Response By August 25, 2026 at 9:36 am UTC, investigation confirmed that the Japan region had not received the required Solution Deployment update and was running an outdated version. A fix was already being prepared. The public status page was updated at August 25, 2026 at 9:41 am UTC to reflect the identified issue and that a fix was being rolled out. At August 25, 2026 at 9:44 am UTC, manual testing confirmed the fix was deployed and working. At August 25, 2026 at 9:47 am UTC, the status page was moved to monitoring. Full recovery was confirmed at August 25, 2026 at 10:13 am UTC, with Solution Deployment operating as expected and no further impact observed. ## Follow up 1. Add documentation and protocols for the frontend framework version upgrade process 2. Add canary tests for both services 3. Add automation that closes the deploy ticket only after everything is verified as working