UiPath experienced a major incident on May 14, 2026 affecting Document Understanding, lasting 1h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 14, 2026, 06:38 PM UTC
We are investigating reports of an outage impacting document processing for [Document Understanding] Impact: Users may be unable to processing documents. Next update: Our teams are working to understand the cause and scope and will share updates as available
- identified May 14, 2026, 07:00 PM UTC
We have identified the cause of the outage impacting document processing for Document Understanding in US and are working on a fix. Impact: Users may continue to be unable to process documents. Next update: Our focus is on restoring service as quickly as possible.
- monitoring May 14, 2026, 07:10 PM UTC
Document processing for Document Understanding in US is recovered and operational, and we are monitoring closely. Next update: We are continuing to monitor system behavior.
- resolved May 14, 2026, 07:43 PM UTC
The outage has been resolved and Document Understanding is fully operational. Impact: No ongoing user impact.
- postmortem Jun 03, 2026, 06:00 AM UTC
## **Customer Impact** Between **May 14, 2026 at 4:17 pm UTC and May 15, 2026 at 12:52 am UTC**, customers using **Document Understanding** in the **U.S. region** experienced intermittent failures and delays when processing documents. The impact was limited to one Document Understanding extraction flow in the U.S. region. Document Understanding services in other geographies were not affected. ## **Root Cause** The incident was caused by an autoscaling issue in an internal component responsible for making extraction models available to processing nodes. During a traffic increase, this component did not scale out. As a result, some processing nodes spent too much time loading or retrying model loads instead of processing extraction requests. This reduced availability for customer traffic and caused intermittent extraction failures and delays. ## **Detection** The issue was detected by automated monitoring on **May 14, 2026 at approximately 4:17 pm UTC**. The incident response process started shortly afterward, and the public status page was updated after the customer impact was confirmed. ## **Response** Engineering teams confirmed that the impact was isolated to Document Understanding extraction traffic in the U.S. region. The team mitigated the issue by increasing available processing capacity where possible, prioritizing customer extraction workloads, and manually scaling the internal model-loading component. After this mitigation, model loading performance improved and the extraction errors rate returned to zero. Recovery was verified through service health dashboards and error-rate monitoring. The incident was marked resolved on **May 15, 2026 at 12:52 am UTC** after the service remained stable with no ongoing customer impact. ## **Follow-Up** To reduce the likelihood and impact of similar incidents, UiPath is taking the following actions: * Improve autoscaling algorithm for the model-loading component so it responds more effectively to sudden increases in demand. * Add monitoring and alerts for model load delays, model load timeouts, and processing nodes delayed by model loading. * Review Document Understanding capacity buffers and scaling assumptions across regions.