UiPath Status

Resolved: The issue has been resolved. The system has remained stable during the monitoring period.

Monitoring: A fix has been deployed and the service is recovering. Current status: We are monitoring the system to ensure stability and full recovery. Further updates will be shared soon

Investigating: We are currently investigating reports of an issue in Integration Service in multiple regions.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Investigating: We are currently investigating reports of an issue in Integration Service in Singapore region.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Resolved: The issue has been resolved.

Monitoring: A fix has been deployed and the service is recovered. Current status: We are monitoring the system to ensure stability and full recovery.

Investigating: New connection creation in UiPath Integration Service is currently failing in the Europe region. Existing connections and running automations are not impacted.

The team is actively working to resolve the issue. We will continue to provide updates on status.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been resolved. The system has remained stable during the monitoring period.

Monitoring: A fix has been deployed and the service is recovering. Current status: We are monitoring the system to ensure stability and full recovery. Further updates will be shared soon

Investigating: We are currently investigating reports of an issue in Integration Service in multiple regions.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Investigating: We are currently investigating reports of an issue in Integration Service in Singapore region.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.