# Changing the solution version

> :::tip
Before upgrading a production deployment, UiPath recommends validating the upgrade in a dedicated test deployment first. For details, see [Validate solution upgrades in a test environment](https://docs.uipath.com/solutions-management/automation-cloud/latest/user-guide/best-practices-test-environment-upgrades).
:::

:::tip
Before upgrading a production deployment, UiPath recommends validating the upgrade in a dedicated test deployment first. For details, see [Validate solution upgrades in a test environment](https://docs.uipath.com/solutions-management/automation-cloud/latest/user-guide/best-practices-test-environment-upgrades).
:::

The **Change version** action lets you upgrade a deployment to a newer package version or downgrade it to an older one (rollback).

Downgrading a solution does not delete entities, choice sets, and webhooks.

## Open the Change version workflow

1. In Orchestrator, select **Solutions** at the tenant level.
2. In the **Deployments** tab, find the deployment you want to update.

   :::tip
   When a newer package version is available for a deployment, the **Version** column shows an upgrade indicator next to the current version number. You can also select **Upgrade** directly from the row to start the flow.
   :::

3. Select the three-dot menu (⋮) at the end of the row, then choose **Change version**.

   The **Change version** workflow opens on the **Setup** form.

## Complete the Setup form

The Setup form is pre-filled with the current deployment details. Review and update the following:

| Field | Description |
|---|---|
| **Package** | The solution package associated with this deployment. Read-only. |
| **Version** | The target package version. Defaults to the latest published version (or the most recent version other than the one currently installed). Select a different version from the dropdown to upgrade or downgrade to a specific version. |
| **Deployment name** | The name of the existing deployment. Read-only. |

Select **Change version** to proceed, or select the dropdown arrow and choose **Customize** to open the resource explorer and review component changes before running the operation.

## Review component changes

When you select **Customize**, the resource explorer shows a summary of what will change:

* **Newly added components**, marked with a plus (+) icon — these components will be created in the target environment after the version change.
* **Removed components**, marked with a minus (−) icon — these components will be removed from the target environment unless they are referenced by other solutions. In that case, the components remain in the environment but are removed from the solution.
* **Edited components**, marked with an asterisk (*) icon — the **Compare property differences** panel highlights all property-level changes.

  Components with changes only to configurable properties are not marked as edited. Edited components retain their existing configuration values for configurable properties by default, but you can switch to using the package configuration. To review all property-level changes, use the **Compare property differences** panel.

Optionally edit any configurable component properties, then select **Continue to change version** to run the operation.

## After the version change

You can monitor the operation status in the **Deployments** tab. For details on all statuses, see [Deployment statuses](https://docs.uipath.com/solutions-management/automation-cloud/latest/user-guide/checking-the-deployment-status).

:::note
After a version change, the deployment status is **Inactive**. Inactive deployments are further classified as **Inactive (Ready to activate)** or **Inactive (Needs setup to activate)**, depending on whether additional configuration is required before activation. You must manually activate the deployment for the solution to become functional.
:::