UiPath Status

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The issue has been resolved and logs are populating as expected.

Monitoring: Logs are now populating as expected in real time and we will continue monitoring the application.

Identified: We identified that robot logs ingestion was delayed. Robot logs are catching up to live data and we are monitoring recovery.

Investigating: We are investigating reports of missing robot logs in the US region. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The issue has been mitigated, and the service is currently operational. We will continue to closely monitor the service health and take further action if needed.

Monitoring: The issue has been mitigated, and the service is currently operational. We will continue to closely monitor the service health and take further action if needed.

Identified: We have identified the issue and implemented the necessary fix

Investigating: We are currently investigation the issue.

Resolved: This issue has been fully resolved and services are stable now. We'll post more details of the incident to status page soon.

Monitoring: We have identified the issue and applied a mitigation. Services are returned back to healthy state and we are monitoring the services.

Investigating: We are investigating reports of degraded performance impacting digitization and extraction for Document Understanding and IXP in US. Impact: Users may experience slowness and failed Document Understanding runtime operations. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: This issue has been fully resolved and services are stable now. We'll post more details of the incident to status page soon.

Monitoring: We have identified the issue and applied a mitigation. Services are returned back to healthy state and we are monitoring the services.

Investigating: We are investigating reports of degraded performance impacting digitization and extraction for Document Understanding and IXP in US. Impact: Users may experience slowness and failed Document Understanding runtime operations. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.