Title: Rollbacks in the VIP Dashboard
Author: WordPress VIP Documentation
Published: September 28, 2023
Last modified: October 16, 2025

---

 1. [Code deployment](https://docs.wpvip.com/code-deployment/)
 2. Rollbacks in the VIP Dashboard

#  Rollbacks in the VIP Dashboard

As an alternative to [reverting a pull request in GitHub](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request),
a rollback to the image of a previous deployment can be performed in [the **Deployments** panel of the VIP Dashboard](https://docs.wpvip.com/vip-dashboard/deployments-panel/)
for a WordPress and Node.js environment.

Restoring the code deployed to an environment to its previous state with a rollback
in the VIP Dashboard is faster than reverting a pull request in GitHub.

When a rollback occurs, an existing image of the selected, previous code deployment
is deployed to the environment. A rollback only deploys the _image_ of the application
code’s previous state to the environment. The state of the application’s GitHub 
repository commit history and the environment’s database remains unchanged.

 * Previous deployments that are eligible for a rollback will display a button in
   the column labeled “**Rollbacks**“.
 * If the code currently deployed to an environment is in a rolled back state, a
   notice will be displayed in [the Overview panel](https://docs.wpvip.com/vip-dashboard/dashboard/)
   and the Deployments panel of the VIP Dashboard.
 * Rollbacks can be performed for a previous deployment that was made with [the Default Deployment method](https://docs.wpvip.com/code-deployment/default-deployment/)
   or with [the Custom Deployment method](https://docs.wpvip.com/code-deployment/custom-deployment/).

## Limitations

The rollback capability is limited to images of:

 * **The three most recent unique deployments to a production environment**, including
   the image that is currently deployed.
 * **The two most recent unique deployments to a non-production environment**, including
   the image that is currently deployed.

## Access

**Prerequisites**

 * All users with [access to an application in the VIP Dashboard](https://docs.wpvip.com/vip-dashboard/vip-dashboard-access/)
   can view the Deployments panel for that application’s environments.
 * A user must have at minimum an [Org member role](https://docs.wpvip.com/roles-and-permissions/)
   or an [App write role](https://docs.wpvip.com/app-role/) for that application
   to:
    - View the complete Build logs in the detailed view of a single deployment.
    - Use the rollback option to restore one of the recent deployments to the environment.

 1. Navigate to the [VIP Dashboard](https://dashboard.wpvip.com/) for an application.
 2. Select an environment from the environment dropdown located at the upper left of
    the VIP Dashboard.
 3. Select “**Deployments**” from the lefthand navigation menu.

## Roll back to a previous deployment

To initiate a rollback to a previous deployment:

 1. Navigate to the [VIP Dashboard](https://dashboard.wpvip.com/) for an application.
 2. Select an environment (e.g., production, develop) from the dropdown located at 
    the upper left of the dashboard.
 3. Select “**Deployments**” from the sidebar navigation at the left of the screen.
 4. Select the button in the column labeled “**Rollbacks**” of an eligible deployment.
 5. In the confirmation dialog, select the button labeled “**Confirm Rollback**“ to
    proceed with the rollback process. To exit the rollback process, the button labeled“**
    Cancel**” can be selected instead.

**Caution**

If a rollback was initiated because of issues that were identified in deployed code,**
those issue should be fixed before any further code is pushed** and before any branches
or tags are created from that code. Failure to do so will result in those issues
being redeployed or duplicated into the new branches or tags.

On an architecture of one repository powering multiple applications (A and B, for
example), a rollback back on application A would only affect application A; application
B would not be rolled back.

Last updated: October 16, 2025