# 2.2510.2 > **Release date: April 15, 2026** **Release date: April 15, 2026** ## Activation strategy option when deploying solutions A new **Activation strategy** option is now available when deploying a solution. This lets you choose whether to activate the deployment immediately or at a later time: - **Now**: The solution is automatically activated right after deployment. - **Later**: You can review the solution and activate it yourself when ready. For more information, see [Deploying a solution](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/deploying-a-solution). ## Streamlined Solutions deployment experience We redesigned the Solutions deployment experience to make the process clearer, more consistent, and easier to use. The previous modal-based deployment flow is replaced with a dedicated **Deploy a solution** page that offers improved navigation, better visibility of deployment options, and a more intuitive structure. For more information, see [Deploying a solution](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/deploying-a-solution). ### What's new #### Deployments is now the default tab The **Deployments** tab is now the default landing view within the Solutions area, making it easier to access deployment actions and track existing deployments. #### New page deployment flow The former deployment modal has been replaced with a dedicated page, providing more space, clearer grouping of settings, and easier access to advanced configuration options. #### Improved deployment entry points You can now start a deployment from multiple surfaces: - **+Deploy** button in the **Deployments** tab. - **Deploy** button in a package row in the **Packages** tab. - **More actions** → **Deploy** menu for any package version. #### New default behaviors - **Activation strategy now defaults to Now**: Deployments automatically activate the solution and its triggers unless you switch to **Later**. - **Deployment location now defaults to Install as root folder**: The solution is installed as a new root folder under the tenant by default, simplifying organization and ensuring clean isolation of solution artifacts. ## 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. Activation validation is now evaluated closer to activation time, ensuring required steps are surfaced and enforced before activation can complete. This reduces manual trial-and-error during deployment activation. For more information, see [Checking the deployment status](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/checking-the-deployment-status). ## Package sidebar for solution packages A new **Package sidebar** is now available in the Solutions experience, making 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 all published versions of the selected package and all deployments associated with that package. You can switch between the **Versions** and **Deployments** tabs, start a new deployment directly from the sidebar, and inspect package status, version history, and deployment state without navigating away. For more information, see [Navigating the Package sidebar](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/navigating-package-sidebar). ## Automatic cleanup of solution debug deployments Solution debug deployments are now automatically uninstalled after 30 days of inactivity. Automatic uninstallation removes all resources created by the deployment and the associated solution folder. This process is managed by Solutions and cannot be configured or disabled. For more information, see [Retention and automatic cleanup of solution debug deployments](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/retention-and-cleanup-of-debug-deployments). ## 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: - A single **Version** column 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**). - 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 reordered to better reflect their relationships. **Activated** and **Version** are now positioned closer to **Name**, while **Operation status** and **Operation started** follow **Last operation**. - The **Operation ended** and **Package name** columns are hidden by default and can be enabled via the **Visible Columns** control. - A new **Location** column shows the folder path where each solution is deployed. - You can filter deployments by multiple status values simultaneously. - When a new package version is available for a deployment, an **Upgrade** icon appears inline so you can upgrade directly from the table. - Two new activation statuses are 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, making it easier to recover from failed or interrupted operations. - You can now create a deployment from the folder context menu (**Actions** > **Add** > **Solution Deployment**) or by selecting **Deploy** on the Orchestrator homepage. For more information, see [Checking the deployment status](https://docs.uipath.com/solutions-management/automation-suite/2.2510/user-guide/checking-the-deployment-status). ## 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 field-level navigation to guide users to the missing configuration.