UiPath Status

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Postmortem: ## Customer impact

Between July 30, 2026 at 10:00 pm UTC and July 31, 2026 at 1:28 am UTC, a subset of customers using Helix models for Document Understanding in the US experienced degraded performance, including failed requests returning HTTP 503 errors and client-side timeouts.

The impact lasted approximately 3 hours and 28 minutes. Some requests continued to process successfully, but affected customers may have seen retries, delayed processing, or failed document extraction and classification jobs.

Root cause

The root cause was duplicate re-processing of the same document pages during a period of high retries. Successful processing results were cached; when the queue was full, failed submissions were not cached. Repeated retries re-entered processing instead of being deduplicated. During the incident window, duplicate processing accounted for the majority of compute work, which drove sustained resource saturation and caused additional 503 responses - which increased load and led to additional 503 responses.

Detection

Automated alerting detected the first queue overflow errors began around 10:00 pm UTC.

Response

At 10:44 pm UTC, we posted an investigation notice for degraded Extraction and Classification performance in the US. By 11:26 pm UTC, we freed capacity by scaling down an unused processing path and freeing additional capacity for the affected Document Understanding workload.

Follow up

1. We plan to implement short-lived failure caching for repeated document submissions, so that duplicate retries after a queue overflow are rejected early instead of re-entering expensive processing.
2. We are improving monitoring and alerting to detect this class of issue sooner.

Resolved: This incident has been resolved. Extraction and Classification for Document Understanding in US are operating normally.

Monitoring: We are continuing to monitor the fix. Performance and error rates have returned to normal levels. We will provide an update once we confirm full recovery.

Monitoring: We have implemented a fix for the degraded performance impacting Extraction and Classification for Document Understanding in US. We are monitoring the results and will provide an update shortly.

Investigating: We are investigating reports of degraded performance impacting Extraction and Classifications for Document Understanding in US. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The issue has been resolved and Agent/Maestro LLM workflow performance has returned to expected levels Impact: No ongoing user impact.

Identified: We have identified that the degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region may be related to a third-party upstream dependency.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are continuing to work with the upstream provider and will share more details as remediation progresses.

Investigating: We are continuing to investigate reports of degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

After applying mitigation steps and monitoring the service, we are still observing latency in some workflows. Our teams are investigating whether an upstream provider may be contributing to the continued latency and will share more details as the investigation progresses.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are continuing to monitor the fix and confirm there is no further impact.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are continuing to monitor the fix for stability and will share more details as needed.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are monitoring the service to confirm continued stability and will share more details as needed.

Identified: We have identified the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may continue to experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are working on a fix and will share more details as remediation progresses.

Investigating: We are investigating reports of degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The issue has been resolved and Agent/Maestro LLM workflow performance has returned to expected levels Impact: No ongoing user impact.

Identified: We have identified that the degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region may be related to a third-party upstream dependency.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are continuing to work with the upstream provider and will share more details as remediation progresses.

Investigating: We are continuing to investigate reports of degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

After applying mitigation steps and monitoring the service, we are still observing latency in some workflows. Our teams are investigating whether an upstream provider may be contributing to the continued latency and will share more details as the investigation progresses.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are continuing to monitor the fix and confirm there is no further impact.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are continuing to monitor the fix for stability and will share more details as needed.

Monitoring: We have implemented a fix for the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may have experienced delayed or failed Agent/Maestro workflow runs when an LLM step was executed.

Our teams are monitoring the service to confirm continued stability and will share more details as needed.

Identified: We have identified the issue causing degraded performance for Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may continue to experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are working on a fix and will share more details as remediation progresses.

Investigating: We are investigating reports of degraded performance impacting Agent/Maestro workflow runs that make LLM calls for Agents in the US region.

Impact: Users may experience delayed or failed Agent/Maestro workflow runs when an LLM step is executed.

Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: All functionality has been restored and the issue is now resolved. Impact: Users should no longer experience issues.

Monitoring: The issue impacting visibility of recent audit log records for AI Trust Layer in the US has been resolved.

The affected aggregation jobs are running successfully, and backfill processing has returned to normal. Audit log ingestion remained healthy throughout the incident.

We will continue to monitor service health. Thank you for your patience.

Identified: The fix remains in place and the affected aggregation jobs are continuing to run successfully.

Impact: Users may still experience delayed visibility of recent records on the AI Trust Layer Audit Log page while the backfill continues. Audit log ingestion remains healthy.

Our teams are continuing to monitor the backfill progress and will share another update once audit log visibility has fully recovered.

Identified: We have applied a fix and are seeing the affected aggregation jobs run successfully again.

Impact: Users may continue to experience delayed visibility of recent records on the AI Trust Layer Audit Log page while processing catches up. Audit log ingestion remains healthy.

Our teams are monitoring the backfill process and will share another update once audit log visibility has fully recovered.

Identified: We have identified the cause of degraded performance impacting visibility of recent audit log records for AI Trust Layer in the US region.

Impact: Users may experience missing or delayed recent records on the AI Trust Layer Audit Log page. Audit log ingestion remains healthy.

Our teams are redeploying the affected service and will continue monitoring recovery. We will share another update as soon as service behavior has stabilized.

Investigating: We are investigating reports of degraded performance impacting visibility of recent audit log records for AI Trust Layer in the US region.

Impact: Users may experience missing or delayed recent records on the AI Trust Layer Audit Log page. Audit log ingestion remains healthy.

Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The mitigation has been deployed across all affected regions and Apps performance has returned to normal. The issue is resolved.

Monitoring: We have a mitigation available and are beginning to roll it out to affected regions. We will provide more updates as the mitigation takes effect.

Identified: We are investigating degraded performance impacting UiPath Apps authored from Studio Web service in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.