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.

Postmortem: ## Customer impact

Between July 22 and July 29, 2026, customers using Document Understanding in the Europe region experienced intermittent delays and, in a limited number of cases, failed document operations. The issue affected document extraction and splitting/classification operations using Helix 2.0-based models— other model types were not affected.

The impact occurred in three windows, each detected by our automated monitoring:

• July 22, approximately 5:10 pm to 7:39 pm UTC
• July 24, approximately 7:45 am to 3:01 pm UTC
• July 29, approximately 10:55 am to 2:05 pm UTC

During these windows, operations that normally complete in under a minute could take several minutes, and a small number of operations failed after all retry attempts. Between the first two windows, a low rate of intermittent delays persisted. The issue was isolated to the Europe region and did not affect other geographies.

Root cause

The root cause was a concurrency issue in the inference service that runs these models. Two stages of processing—preparing incoming requests and generating results—shared an internal component that only one operation can use at a time. Under high-load, operations queued for this shared component, slowing result generation even though compute capacity was available. Slow operations kept their processing slots occupied, so new requests queued behind them and some were rejected, and a small number of operations ultimately failed after exhausting all retry attempts. Large, image-heavy documents increased use of the shared component and made the slowdown worse.

Retried requests for the same document are automatically deduplicated, so retries did not multiply the processing work; however, rejected requests did not tell clients when to retry, which added some pressure during the constrained periods.

The July 29 recurrence happened because a protective configuration change applied after the earlier occurrences was unintentionally reverted during a routine deployment. It was re-applied the same day and has now been made permanent.

Detection

Automated alerts detected the initial issue at 5:14 pm UTC on July 22, approximately four minutes after failures began to rise. Monitoring showed elevated failed requests and longer processing times.

After the first window was resolved, our engineering team continued to track a low rate of intermittent delays through end-to-end tests and telemetry reviews while the investigation continued. A new automated alert detected the July 24 recurrence, and the July 29 recurrence was detected by automated alerts within minutes of onset.

Response

On July 22, automated capacity scaling restored throughput and the failure rate returned to near-baseline levels. The status page was updated at 5:45 pm UTC, and after continued monitoring showed no further customer-visible failures, the incident was closed at 7:39 pm UTC. After closure, our engineering team continued investigating the underlying cause—that investigation was still in progress when the issue recurred on July 24.

On July 24, following the recurrence, our engineering team restarted the affected inference workers and applied a protective configuration change that reduces concurrent processing per worker and increases minimum capacity. The status page was updated at 9:22 am UTC, and the incident was resolved at 3:01 pm UTC after extended monitoring.

On July 29, engineers identified that the protective configuration had been unintentionally reverted, re-applied it, and restarted the affected workers. The status page was updated at 11:54 am UTC. Service was confirmed stable—including by affected customers—and the incident was resolved at 2:05 pm UTC.

Follow-up

We are taking the following steps to prevent recurrence and improve resilience:

1. Retry handling: Rejected requests now include explicit retry-timing guidance so that clients back off appropriately during constrained periods. Requests for the same document remain automatically deduplicated, so retries do not multiply processing work.
2. Contention fix: We have completed a code change that removes the internal contention that caused slow processing under high loads. It is being rolled out and validated under production traffic.
3. Configuration safeguards: The protective configuration has been made permanent in our deployment configuration, with change controls in place so that it cannot be unintentionally reverted.
4. Observability and alerting: We are improving monitoring and alerting to detect this class of issue sooner, and tightening incident-closure criteria so that incidents are not closed while residual degradation remains.

Resolved: The fix has been successfully applied, and our monitoring confirms that Extraction and Classifications for Document Understanding in Europe are operating normally. This incident has been resolved.

Monitoring: We have applied the fix, we are currently monitoring the situation closely.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating reports of degraded performance impacting Extraction and Classifications for Document Understanding in Europe. 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: 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 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 4:32 am UTC and 8:12 am UTC (approximately 3 hours and 40 minutes), a subset of customers in the Asia-Pacific region - Japan, Australia, and Singapore - experienced degraded Insights behavior for recently created queue items. These items could not be processed by the Insights data pipeline because their folder association was missing. No data was lost, and all affected items were recovered.

Root cause

The root cause was a planned database maintenance intended to clean up folder references that pointed to deleted folders or classic folders. This work was meant to proactively fix recurring tenant-migration problems and reduce the remaining references to classic folders, a prerequisite for removing them.

Unintentionally, the change left some active queue definitions without a folder association, and newly created queue items copied that missing association. As a result, the Insights data pipeline could not process those queue items until the associations were restored.

Detection

The issue was detected by automated alerting on July 30, 2026 at 4:32 am UTC, when an alert reported an extended pipeline failure in the Insights backend. Detection occurred at the same time the incident was opened. The public status page was updated at 4:42 am UTC.

Response

By 5:14 am UTC, analysis confirmed that the issue affected a subset of recently created queue items, that no data had been lost, and that all affected items could be recovered. At 6:17 am UTC, a recovery script was prepared to restore valid folder associations on queue definitions. At 6:22 am UTC, validation of the fix began before applying it to affected queue items.

Recovery was applied region by region. Japan was fixed by 7:16 am UTC and confirmed recovered at 7:42 am UTC. Australia was completed at 7:49 am UTC, and all three impacted regions were reported resolved at 7:55 am UTC. By 8:12 am UTC, the fix had been applied to all impacted regions and affected items had been recovered.

As a precaution, the same recovery was then applied to remaining regions where the cleanup had run. This precautionary work was completed by 11:00 am UTC, monitoring began at 11:12 am UTC, and the incident was resolved at 12:30 pm UTC after monitoring confirmed normal operation.

Follow up

Our goal is to ensure that routine database maintenance can no longer leave an active queue definition without a valid main folder association, and that any similar issue is detected and recovered before it affects customers. To achieve this, the following preventive actions are being tackled:

1. Add pre-execution validation and staged, region-by-region rollout to folder-cleanup maintenance, so active queue definitions always retain a valid main folder association.
2. Maintain a validated recovery procedure to quickly restore folder associations if a similar issue occurs.

Resolved: The fix has been applied across all regions and all affected items have been recovered. Monitoring is complete and all systems are operating normally. The issue is resolved.

Monitoring: The fix has been applied across all regions and we're monitoring to confirm full stability.

Identified: The precautionary rollout to remaining regions is still in progress.

Identified: We're still rolling the same fix out to remaining regions as a precaution. No further customer impact is expected.

Identified: The fix has been applied to all impacted regions and the affected items have been recovered. As a precaution, we're rolling the same fix out to remaining regions. No further customer impact is expected.

Identified: Recovery is complete in Japan and we're validating the changes. We'll apply the same fix to the remaining regions and update as each completes.

Identified: We've prepared a fix and are validating it before applying it to affected queue items. We'll post again once recovery is underway

Identified: We've identified the cause of an issue affecting a subset of recently created queue items. No data has been lost, and we've confirmed all affected items can be fully recovered. We're validating a fix and will begin recovery shortly.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating degraded performance impacting Insights Service in Japan, Singapore and Australia Region. 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.

Postmortem: ## Customer impact

Between July 30, 2026 at 4:32 am UTC and 8:12 am UTC (approximately 3 hours and 40 minutes), a subset of customers in the Asia-Pacific region - Japan, Australia, and Singapore - experienced degraded Insights behavior for recently created queue items. These items could not be processed by the Insights data pipeline because their folder association was missing. No data was lost, and all affected items were recovered.

Root cause

The root cause was a planned database maintenance intended to clean up folder references that pointed to deleted folders or classic folders. This work was meant to proactively fix recurring tenant-migration problems and reduce the remaining references to classic folders, a prerequisite for removing them.

Unintentionally, the change left some active queue definitions without a folder association, and newly created queue items copied that missing association. As a result, the Insights data pipeline could not process those queue items until the associations were restored.

Detection

The issue was detected by automated alerting on July 30, 2026 at 4:32 am UTC, when an alert reported an extended pipeline failure in the Insights backend. Detection occurred at the same time the incident was opened. The public status page was updated at 4:42 am UTC.

Response

By 5:14 am UTC, analysis confirmed that the issue affected a subset of recently created queue items, that no data had been lost, and that all affected items could be recovered. At 6:17 am UTC, a recovery script was prepared to restore valid folder associations on queue definitions. At 6:22 am UTC, validation of the fix began before applying it to affected queue items.

Recovery was applied region by region. Japan was fixed by 7:16 am UTC and confirmed recovered at 7:42 am UTC. Australia was completed at 7:49 am UTC, and all three impacted regions were reported resolved at 7:55 am UTC. By 8:12 am UTC, the fix had been applied to all impacted regions and affected items had been recovered.

As a precaution, the same recovery was then applied to remaining regions where the cleanup had run. This precautionary work was completed by 11:00 am UTC, monitoring began at 11:12 am UTC, and the incident was resolved at 12:30 pm UTC after monitoring confirmed normal operation.

Follow up

Our goal is to ensure that routine database maintenance can no longer leave an active queue definition without a valid main folder association, and that any similar issue is detected and recovered before it affects customers. To achieve this, the following preventive actions are being tackled:

1. Add pre-execution validation and staged, region-by-region rollout to folder-cleanup maintenance, so active queue definitions always retain a valid main folder association.
2. Maintain a validated recovery procedure to quickly restore folder associations if a similar issue occurs.

Resolved: The fix has been applied across all regions and all affected items have been recovered. Monitoring is complete and all systems are operating normally. The issue is resolved.

Monitoring: The fix has been applied across all regions and we're monitoring to confirm full stability.

Identified: The precautionary rollout to remaining regions is still in progress.

Identified: We're still rolling the same fix out to remaining regions as a precaution. No further customer impact is expected.

Identified: The fix has been applied to all impacted regions and the affected items have been recovered. As a precaution, we're rolling the same fix out to remaining regions. No further customer impact is expected.

Identified: Recovery is complete in Japan and we're validating the changes. We'll apply the same fix to the remaining regions and update as each completes.

Identified: We've prepared a fix and are validating it before applying it to affected queue items. We'll post again once recovery is underway

Identified: We've identified the cause of an issue affecting a subset of recently created queue items. No data has been lost, and we've confirmed all affected items can be fully recovered. We're validating a fix and will begin recovery shortly.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating degraded performance impacting Insights Service in Japan, Singapore and Australia Region. 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.