---
title: "Rolling back a deployment | Jetstack AI Docs"
description: "Roll back a Portal reuse deployment: preview what will be removed, then delete the assets the deployment created, with shared and edited assets protected."
url: "https://jetstack.ai/docs/implementations/deploying/rollback/"
---

# Rolling back a deployment

You can roll back a deployment you made from the Asset Library. Jetstack AI shows you what will be removed first, then deletes the assets that deployment **created** in the destination portal.

## What a rollback removes

- **Assets the deployment created** in the destination portal are deleted.
- **Existing assets the deployment matched and reused** are not deleted. They were already in the portal before you deployed.
- Each asset’s result is recorded in the [Activity Log](https://jetstack.ai/docs/account/activity/details), so you can see what was removed and what was kept.

## What a rollback protects

A rollback won’t delete an asset when doing so could break something else:

| Situation                                                        | What happens                                          |
| ---------------------------------------------------------------- | ----------------------------------------------------- |
| Another deployment or a Project in Jetstack still uses the asset | Refused, and the other deployment or Project is named |
| The asset was edited in HubSpot after the deployment             | Skipped, so the later changes aren’t lost             |
| A page, blog post or HubDB table is published                    | Unpublish it in HubSpot first, then roll back         |
| Another rollback of the same deployment is running               | The second one waits; only one runs at a time         |

## Roll back a deployment

1. Open the deployment in the **Activity Log** in the Jetstack app, or from the task list in the [Chrome extension](https://jetstack.ai/docs/extension/tasks).
2. Choose **Rollback**. Jetstack prepares a preview of every asset it will delete and every asset it will keep, with the reason.
3. Review the preview, then confirm.
4. Check the per-asset results when the rollback finishes.

If a rollback stops part-way (for example, the browser closes during an extension rollback), you can start it again; assets already removed stay removed.

A rollback removes configuration, not what that configuration already did. Emails a workflow sent, records it updated and data that flowed through an integration stay as they are. If a deployed workflow has already run, turn it off and review its effects as well.

## Projects

Assets a [Project](https://jetstack.ai/docs/projects) deployed are managed from the Project itself: a Project asset can be retired or removed there. A Portal reuse rollback won’t delete an asset a Project still holds.
