UiPath Status

Resolved: The issue is now resolved. Customers in other regions may have seen disruptions during the affected period, and we are monitoring to confirm that everything remains stable.

Monitoring: Some users in other regions may have been disrupted due to this issue. The issue now appears to be resolved, and we are monitoring to ensure that services remain stable.

Identified: We have applied a fix and are monitoring error levels to confirm that the service is recovering as expected. We will provide another update once we verify stable performance.

Investigating: We are actively investigating a service issue that is currently affecting customers who rely on KMS integration in our Europe region. Our engineering teams are investigating the issue and are working to understand the scope and root cause. We will continue to provide updates as we learn more and move toward a full resolution.

Resolved: The issue has now been resolved in all regions. Thank you for your patience throughout the incident.

Identified: Deployment has been completed in the high traffic regions and the issue has been fixed and validated. We are now proceeding with deployment in the remaining regions.

Identified: We have validated the fix in lower environments and will now proceed with deploying it across all regions. We will provide more updates as the rollout continues.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have validated the fix in lower environments and will now proceed with deploying it across all regions. We will provide more updates as the rollout continues.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified a fix and we are still working to get it deployed. We will share more details as progress continues. Thank you for your patience while we work to resolve this.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified a fix and are working to get it deployed. We will share more details as progress continues. Thank you for your patience while we work to resolve this.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: We are still investigating this issue and will share more information as soon as it is available.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: Update: Only event triggers are affected by this issue. Other trigger types continue to function normally. We recommend avoiding edits to event triggers until the mitigation is complete.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: We are currently seeing an issue where editing triggers can lead to unexpected behavior. Our team is investigating to restore normal operation.

When editing triggers in Orchestrator, the underlying triggers may be removed due to an ongoing issue. We recommend avoiding any edits during this period. If a change is necessary, you can create a new trigger after disabling the current one so that no events are lost.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Resolved: The problem has been addressed and normal functionality has been restored across all environments. We have confirmed that the affected services are working as expected.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We are continuing to roll out the fix through all of our environments.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: The rollout is still underway while we complete validation in earlier environments. We will advance once those checks are finished.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We are still in the process of deploying the fix and will share another update once the rollout advances.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified the issue and are rolling out a fix. We will provide more updates as the rollout progresses.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: Enabling or disabling Event Triggers is currently failing. Our team is investigating the issue. Integration Service and Solutions Management are affected in all regions. This problem also impacts the activation of Solutions.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Resolved: The issue has now been resolved in all regions. Thank you for your patience throughout the incident.

Identified: Deployment has been completed in the high traffic regions and the issue has been fixed and validated. We are now proceeding with deployment in the remaining regions.

Identified: We have validated the fix in lower environments and will now proceed with deploying it across all regions. We will provide more updates as the rollout continues.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have validated the fix in lower environments and will now proceed with deploying it across all regions. We will provide more updates as the rollout continues.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified a fix and we are still working to get it deployed. We will share more details as progress continues. Thank you for your patience while we work to resolve this.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified a fix and are working to get it deployed. We will share more details as progress continues. Thank you for your patience while we work to resolve this.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: We are still investigating this issue and will share more information as soon as it is available.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: Update: Only event triggers are affected by this issue. Other trigger types continue to function normally. We recommend avoiding edits to event triggers until the mitigation is complete.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: We are currently seeing an issue where editing triggers can lead to unexpected behavior. Our team is investigating to restore normal operation.

When editing triggers in Orchestrator, the underlying triggers may be removed due to an ongoing issue. We recommend avoiding any edits during this period. If a change is necessary, you can create a new trigger after disabling the current one so that no events are lost.

This issue is affecting all regions at this time. Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Postmortem: Customer Impact
Between Nov 14 12:00 UTC and Nov 14 13:00 UTC, the Solutions Management UI became temporarily inaccessible following a routine Orchestrator deployment. During this period, customers were unable to access the Solutions Management interface, while all backend APIs and other Orchestrator functionalities remained available.

Root Cause
An untracked dependency between the Orchestrator and Solutions components caused a compatibility mismatch after the Orchestrator update. This dependency had not been captured in deployment sequencing, leading to the UI becoming inaccessible once the new version was released.

Detection
Internal monitoring quickly identified that the Solutions Management UI was unavailable shortly after deployment.

Response
The engineering team promptly investigated and identified the dependency issue. The problem was resolved by restoring compatibility between the components, and normal access to the Solutions Management UI was fully restored.

Follow-Up Actions
To prevent recurrence, the dependency has been documented and incorporated into our deployment process.
Additionally, we are planning to include this specific scenario in our canary test suite to ensure early detection of similar issues in future deployments.

Resolved: Incident is Resolved

Monitoring: A fix has been applied, and the team is currently monitoring the system to ensure stability

Identified: Solutions Management is currently inaccessible for Community users in the Europe region. Our team has identified the issue and is working on a fix. The API endpoint remains operational and is functioning as expected

Resolved: The problem has been addressed and normal functionality has been restored across all environments. We have confirmed that the affected services are working as expected.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We are continuing to roll out the fix through all of our environments.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: The rollout is still underway while we complete validation in earlier environments. We will advance once those checks are finished.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We are still in the process of deploying the fix and will share another update once the rollout advances.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Identified: We have identified the issue and are rolling out a fix. We will provide more updates as the rollout progresses.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: Enabling or disabling Event Triggers is currently failing. Our team is investigating the issue. Integration Service and Solutions Management are affected in all regions. This problem also impacts the activation of Solutions.

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Resolved: We identified the root cause of the issue affecting a small group of customers using the preview feature. A temporary workaround was applied over the weekend while we prepared the permanent fix. The permanent fix has now been deployed and the service is operating normally. We appreciate your patience and apologize for any disruption.

Identified: We have confirmed this issue impacts a limited subset of customers who are currently using this preview feature. We have identified both the root cause and a temporary workaround.

The workaround will remain in effect over the weekend, and the permanent fix is scheduled for deployment on Monday. We apologize for any disruption this may have caused and appreciate your patience.

Temporary Workaround Details: To unblock the design time operation, affected customers can perform the following steps:

1. Remove or rename the File argument within the agents.
2. Re-run the agents after making this change.

Identified: Our team has identified the issue and is working on the fix. We will provide additional updates when available.

Investigating: When users use File Attachment feature (in preview) of Agents, when a file is uploaded and then removed, it will block all further design time operations on that agent project. This does not affect the already deployed agents. As a workaround, removing or renaming the File argument and re-running the agent should unblock design time operation.