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
Section titled “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, so you can see what was removed and what was kept.
What a rollback protects
Section titled “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
Section titled “Roll back a deployment”- Open the deployment in the Activity Log in the Jetstack app, or from the task list in the Chrome extension.
- Choose Rollback. Jetstack prepares a preview of every asset it will delete and every asset it will keep, with the reason.
- Review the preview, then confirm.
- 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.
Projects
Section titled “Projects”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.