Skip to content

Rollbacks in the VIP Dashboard

As an alternative to reverting a pull request in GitHub, a rollback to a previous deployment can be performed in the Deployments panel of the VIP Dashboard for an environment. Rollbacks can be performed for a previous deployment that was made with the Default Deployment method or with the Custom Deployment method.

Previous deployments that are eligible for a rollback will display a button in the column labeled “Rollbacks“. The rollback capability for WordPress and Node.js environments is limited to:

  • The most recent 6 deployments for a production environment.
  • The most recent 3 deployments for non-production environments.

When a rollback occurs, an existing image of the selected, previous code deployment is deployed to the environment. Only that previous state of application code is deployed to the environment—the state of the environment’s database remains unchanged. If Default Deployment is enabled, the state of an application’s GitHub repository commit history also remains unchanged.

If the code currently deployed to an environment is in a rolled back state, a notice will be displayed in the Overview panel and the Deployments panel of the VIP Dashboard.



  • All users with access to an application in the VIP Dashboard can view the Deployments panel for that application’s environments.
  • A user must have at minimum an Org member role or an App write 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 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 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.


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: June 25, 2024

Relevant to

  • Node.js
  • WordPress