February 2026

16 February, 2026

Bug fixes

We fixed an issue where validation errors for Assets were not surfaced during solution deployment when required fields were missing. The system now correctly marks such cases with 'requiresConfiguration: true', ensuring the error is displayed and enabling proper field-level navigation to guide users to the missing configuration.

11 February, 2026

Introducing data residency in Switzerland for UiPath Solutions

As part of our ongoing cloud expansion, we are bringing complete data sovereignty to the Switzerland region for Solutions. This ensures your data is securely stored and replicated across multiple availability zones within Switzerland, offering full control and compliance confidence. For more information, refer to the Data Residency page.

05 February, 2026

Enhanced user experience on the Deployments tab

We simplified the Deployments experience to reduce visual clutter and make common actions easier to find.

Key changes include:

• Several updates to the Deployments table:
  • A single Version column in the Deployments table now replaces the previous Now version and Current version columns. If multiple versions apply, previous and current versions appear in the same column.
  • The Status column now displays plain text values (for example, Successful, Draft, Failed) while status icons are now removed.
  • Column names were updated for clarity: Last Operation, Status, Started, and Ended were renamed to Last operation, Operation status, Operation started, and Operation ended.
  • Columns were also reordered to better reflect their relationships. Activated and Version are now positioned closer to Name, while Operation status and Operation started were moved after Last operation. This change helps reduce confusion. For example, a Draft status now clearly refers to the operation, not the deployment itself.
  • The Operation ended and Package name columns are hidden by default (they can still be enabled via the Visible Columns control).
  • New Location column shows the folder path where each solution is deployed.
• You can filter deployments by multiple status values simultaneously (for example, In progress + Successful).
• When a new package version is available for a deployment, an Upgrade icon appears inline so you can upgrade directly from the table.
• Activation-related statuses are consolidated and clarified to make it easier to identify deployments that need activation or have activation failures with two new statuses being introduced: Inactive (Needs setup to activate) and Inactive (Ready to activate).
• For Draft deployments, the Actions menu now includes both the standard draft actions and the actions associated with the previous operation (from before the deployment transitioned to Draft). This provides continuity with the deployment’s last execution state and makes it easier to recover from failed or interrupted operations without restarting the deployment flow.
• You now have multiple ways to create a deployment: either from the folder context menu (Actions -> Add -> Solution Deployment) or by selecting Deploy on the Orchestrator homepage (available at tenant and folder levels).

03 February, 2026

Streamlined workflow for activation setup

We improved the activation experience for solution deployments by refining how inactive deployments are represented and validated. Inactive deployments are now distinguished based on activation readiness:

• Inactive (Needs setup to activate): the deployment requires additional configuration before it can be activated, such as authenticating a packaged connection.
• Inactive (Ready to activate): the deployment meets all activation requirements and can be activated directly.

For deployments that require setup, activation validation is evaluated closer to activation, ensuring required steps are identified and enforced before activation can complete. This helps surface configuration requirements ealier and reduces manual trial-and-error during deployment activation.

As part of this improvement, the activation flow was streamlined by no longer enforcing certain optional configuration setps during activation (specifically, defining account-machine mappings and setting per-robot asset values). These configurations may still be required depending on the solution and are documented separately as optional post-deployment steps.

Package sidebar for solution packages

We introduced a new Package sidebar in the Solutions experience to make it easier to explore package details and manage deployments without leaving the Packages page.

When you select a solution package on the Packages tab, a contextual sidebar displays the following:

• All published versions of the selected package
• All deployments associated with that package

The sidebar consolidates previously standalone pages into a single, dynamic view and allows you to:

• Switch between Versions and Deployments for the selected package
• Start a new deployment directly from the sidebar
• Quickly inspect package status, version history, and deployment state When a solution is published successfully from Studio Web, you are automatically redirected to Orchestrator > Solutions > Packages tab, with the Package sidebar open for the newly published package.

This improvement streamlines package navigation and reduces context switching when managing solution versions and deployments.

Automatic cleanup of solution debug deployments

Solution debug deployments are now automatically uninstalled after a period of inactivity. If a solution debug deployment has not been used for 30 days, the system automatically uninstalls it. This cleanup removes the following:

• All resources created by the solution deployment
• The solution folder associated with the deployment

The cleanup process is managed by Solutions and cannot be configured or disabled by users.