UiPath Status

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: We have confirmed that the rollback has completed and the issue affecting low-code agents that use solution-local action apps for community users in Europe has been resolved. Services have recovered, and we are closing this incident.

Identified: We have identified the issue causing failures in low-code agents that use solution-local action apps for community users in Europe. We are rolling back the previous changes and continuing to monitor the recovery. We will provide another update once rollback is complete or if we have additional information to share.

Investigating: Starting October 1 at approximately 12:00 PM UTC, community users in Europe may experience failures in LowCode Agents that use solution-local Action Apps. We have confirmed the impact is limited to community users in Europe. We are actively investigating the issue, determining the extent of the failures, and working on a fix.

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: We have reverted the change that caused this issue and confirmed that the affected models are available again. Some agents may continue to experience intermittent failures while instances refresh. We are continuing to monitor agent design and execution for gemini-3.1-pro-preview and gpt-4o-2024-05-13.

Identified: We have identified the issue and are deploying a fix. Agents using the affected models may continue to experience failures, and the models may remain unavailable for selection during agent design, while the deployment completes.

Investigating: Starting October 1 at approximately 1:30 PM UTC, some Agents, including both low-code and coded agents, began experiencing failures across all regions when using gemini-3.1-pro-preview and gpt-4o-2024-05-13. These models may also be unavailable for selection during agent design. We are actively investigating and working on a fix.

Resolved: The degraded performance affecting Orchestrator and Action Center in the US region has been resolved. System performance has remained stable following the implemented fix, and we will continue standard monitoring.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. Our team is actively monitoring the results to confirm the issue is fully resolved.

Identified: A fix is currently being deployed for the degraded performance affecting Orchestrator and Action Center in the US region. Further updates will follow.

Investigating: Our team is actively working on a fix for the degraded performance affecting Orchestrator in the US region. We will share updates as progress is made.

Resolved: This issue has been resolved. Between 15:05 and 16:39 UTC, jobs on Cloud Robots in the US region were slow to start or stayed in the Pending state. Jobs have been starting normally since 16:39 UTC, and jobs that were delayed during this time have now been processed. We apologize for the disruption.

Monitoring: After further work on the issue, jobs on Cloud Robots in the US region are now starting normally. Jobs that were delayed earlier are being processed. We're continuing to monitor the service and will post another update once the issue is resolved.

Monitoring: We've applied a fix for the issue that delayed jobs on Cloud Robots in the US region, and jobs are starting normally again. Jobs that were delayed are now being processed. We're monitoring to make sure the service stays stable and will post another update within 60 minutes.

Investigating: Since about 15:05 UTC, some customers in the US region may see jobs that run on Cloud Robots take longer than usual to start, or stay in the Pending state. Jobs on your own robots are not affected, and neither are other regions. We've found the likely cause and are working to restore normal job processing. Jobs that are already queued are not lost and will be processed once the issue is resolved. We'll post another update within 60 minutes.

Resolved: The degraded performance affecting Orchestrator and Action Center in the US region has been resolved. System performance has remained stable following the implemented fix, and we will continue standard monitoring.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.

Monitoring: A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. Our team is actively monitoring the results to confirm the issue is fully resolved.

Identified: A fix is currently being deployed for the degraded performance affecting Orchestrator and Action Center in the US region. Further updates will follow.

Investigating: Our team is actively working on a fix for the degraded performance affecting Orchestrator in the US region. We will share updates as progress is made.

Resolved: This issue has been resolved. Between 15:05 and 16:39 UTC, jobs on Cloud Robots in the US region were slow to start or stayed in the Pending state. Jobs have been starting normally since 16:39 UTC, and jobs that were delayed during this time have now been processed. We apologize for the disruption.

Monitoring: After further work on the issue, jobs on Cloud Robots in the US region are now starting normally. Jobs that were delayed earlier are being processed. We're continuing to monitor the service and will post another update once the issue is resolved.

Monitoring: We've applied a fix for the issue that delayed jobs on Cloud Robots in the US region, and jobs are starting normally again. Jobs that were delayed are now being processed. We're monitoring to make sure the service stays stable and will post another update within 60 minutes.

Investigating: Since about 15:05 UTC, some customers in the US region may see jobs that run on Cloud Robots take longer than usual to start, or stay in the Pending state. Jobs on your own robots are not affected, and neither are other regions. We've found the likely cause and are working to restore normal job processing. Jobs that are already queued are not lost and will be processed once the issue is resolved. We'll post another update within 60 minutes.

Resolved: We have reverted the change that caused this issue and confirmed that the affected models are available again. Some agents may continue to experience intermittent failures while instances refresh. We are continuing to monitor agent design and execution for gemini-3.1-pro-preview and gpt-4o-2024-05-13.

Identified: We have identified the issue and are deploying a fix. Agents using the affected models may continue to experience failures, and the models may remain unavailable for selection during agent design, while the deployment completes.

Investigating: Starting October 1 at approximately 1:30 PM UTC, some Agents, including both low-code and coded agents, began experiencing failures across all regions when using gemini-3.1-pro-preview and gpt-4o-2024-05-13. These models may also be unavailable for selection during agent design. We are actively investigating and working on a fix.

Resolved: We have reverted the change that caused this issue and confirmed that the affected models are available again. Some agents may continue to experience intermittent failures while instances refresh. We are continuing to monitor agent design and execution for gemini-3.1-pro-preview and gpt-4o-2024-05-13.

Identified: We have identified the issue and are deploying a fix. Agents using the affected models may continue to experience failures, and the models may remain unavailable for selection during agent design, while the deployment completes.

Investigating: Starting October 1 at approximately 1:30 PM UTC, some Agents, including both low-code and coded agents, began experiencing failures across all regions when using gemini-3.1-pro-preview and gpt-4o-2024-05-13. These models may also be unavailable for selection during agent design. We are actively investigating and working on a fix.

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

Resolved: We have reverted the change that caused this issue and confirmed that the affected models are available again. Some agents may continue to experience intermittent failures while instances refresh. We are continuing to monitor agent design and execution for gemini-3.1-pro-preview and gpt-4o-2024-05-13.

Identified: We have identified the issue and are deploying a fix. Agents using the affected models may continue to experience failures, and the models may remain unavailable for selection during agent design, while the deployment completes.

Investigating: Starting October 1 at approximately 1:30 PM UTC, some Agents, including both low-code and coded agents, began experiencing failures across all regions when using gemini-3.1-pro-preview and gpt-4o-2024-05-13. These models may also be unavailable for selection during agent design. We are actively investigating and working on a fix.

Resolved: The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Monitoring: We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

Monitoring: A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

Investigating: We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.