All Collections
Using Salto
Deploying Changes
Restoring an environment to a previous version
Restoring an environment to a previous version
Support avatar
Written by Support
Updated over a week ago

Occasionally, you may want to restore some of your environment configuration to a previous version. You may want to restore these changes after refreshing a sandbox, troubleshoot an issue with your environment, or any other reason.

This flow allows you to compare your environment’s current state with a previous version and manually select elements you would like to restore.

To revert Salto deployments, please refer to “Reverting deployments

To restore environment configuration to a previous version, go to the Compare & Deploy tab, in the deployment history table, click on the blue triangle at the top right choose "Restore to a previous version" and then click on “Restore to a previous version”.

Select an earlier version of the environment for comparison with the latest version. Note that previous versions of the environment configuration are available per each successful fetch of that environment.

Once the deployment is created, choose which changes in the environment you would like to restore. If you cannot find the changes you would like to restore you can modify the earlier version of the environment by clicking on the version badge.

Important Notice on Restoring with Regenerated Salto IDs

When fetching an environment with the option to regenerate Salto IDs enabled, be mindful that attempting to restore to a version prior to this fetch may result in elements with newly generated Salto IDs not being restored. This limitation is due to the absence of these IDs in earlier versions, which can prevent a direct match during the restoration process. Please plan your restoration activities accordingly to make sure you recover the environment's configuration.

After selecting the changes you wish to deploy, click "Preview Deployment" to continue. You can read more about the rest of the deploy process, in the "Comparing and Deploying changes" help article.

Did this answer your question?