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.

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: 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.