> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/patching-fundamentals/flex-controls/flex-controls-rollbacks.md).

# Rollbacks

You may also rollback one or more patches or releases to an earlier, non-sequential version. In either case, you may configure Rollback activities across your entire estate or limit a rollback to one or more Business Units.

If a rollback is defined for a patch on a business unit, it sets the desired state of the target clients to **Rollback**. The client will then check if its current scan state is out of sync with that desired state.

If the client's installed version does not match the rollback target version, the client will queue a rollback deployment to bring the patch to the target version. This continues to be enforced as long as the rollback desired state is active. If a scan returns a version that is not the rollback target, the system will attempt to remediate it by performing the rollback.

![](/files/y8rytE4ZQ5rKazw7Q1WX)

## Create a Rollback

1. Select the **Advanced Settings > Flex Controls > Rollbacks** from the side navigation
2. Click **+New**
3. Enter a unique **Name** and **Description**.
4. Select **Browse** to select the product you'd like to rollback.

   ![](/files/UpJVKmtTPURLYMQZ7KjS)
5. (Optional) Click **Browse** to select the **Rollback Target** then select the version you want to rollback to.

   If you do not select a specific version and leave **Rollback Target** blank, you will default to the last accepted version.
6. Select the desired version from the **Installable Software** table.
7. Click **OK**.
8. Select **Browse** to choose which Business Units you would like to apply to this rollback.
9. Click **OK**.
10. Click **Save**.

    ![](/files/ow2j2ShP3P7K1E8O9r6U)

You have now created a rollback that will apply to a client device during the next scan.

## Validate Rollback

In order to test if your rollback was successful, you can apply a manual [Scan](/patch/patching-fundamentals/flex-controls/flex-controls-scan-requests.md) and verify which version displays in the [Devices dashboard](/patch/get-started/dashboards.md#devices).

1. Select **Asset Management > Devices** then select a device from the **Device Status** table to open the **Per-Device Patching State** dashboard.
2. Select the **Scan** button above the **Device Activity** timeline.

   ![](/files/NEyCtqhk9CrfpHJF27SG)
3. Select **Browse** next to **Target Business Units** and select which business units you would like to verify.
   * If you would like to select individual clients, select **Browse** next to **Target Clients** instead of **Target Business Units**.
4. (Optional) Select **Browse** next to **Patching Strategies** to select the strategy that your product is included.
5. Toggle **ON** **Scan All Software**, however, this will take longer and is more resource intensive depending on your device's products.
6. (Optional) Toggle **ON** **Reset Data** if you want scan data for clients cleared from the Adaptiva Server and Client and repopulated with the requested scan.
   * Recommended only if having issues with scan.
7. Select **Browse** to select the software product(s) you'd like to scan included in your rollback.

   ![](/files/G3NDVJTfE4LaY6uRdSzT)
8. Click **OK**.
9. You can track the progress of the scan and rollback from the **Device Activity** timeline.

   ![](/files/dWwOOx2pJrpXf4TZZ95v)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adaptiva.com/patch/patching-fundamentals/flex-controls/flex-controls-rollbacks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.