Skip to content

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.

  • 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, so you can see what was removed and what was kept.

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

SituationWhat happens
Another deployment or a Project in Jetstack still uses the assetRefused, and the other deployment or Project is named
The asset was edited in HubSpot after the deploymentSkipped, so the later changes aren’t lost
A page, blog post or HubDB table is publishedUnpublish it in HubSpot first, then roll back
Another rollback of the same deployment is runningThe second one waits; only one runs at a time
  1. Open the deployment in the Activity Log in the Jetstack app, or from the task list in the Chrome extension.
  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.

Assets a Project 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.