This flow allows you to compare your application connection’s current state with a previous version and manually select elements you would like to restore.
To revert Tulip deployments, please refer to “Reverting deployments”
Occasionally, you may want to restore some of your application connection configuration to a previous version. You may want to restore these changes when a security issue occurs in production and you want to go back to the last working version, after refreshing a sandbox, or for other operational or compliance reasons.
To restore an application connection's configuration to a previous version, go to the History page. Here, you'll see two tabs: "Snapshots" and "Changes". The "Snapshots" tab displays all saved versions for the application connection.
To restore the application connection's configuration to a specific version, hover on the row of the Fetch or Deployment that changed the application connection and click the Restore button:
A "Restore" deployment will then be created. The deployment starts with a comparison of the current application connection configuration and the historic configuration from the version you chose; you can now select specific changes you want to restore.
💡 A version is created after every successful fetch and deployment that represents changes in the application connection.
To learn more about automating and controlling your versions frequency go to "Fetching Your Configuration Data".
If you cannot find the changes you would like to restore, you can modify the compared version of the application connection by clicking on the version badge and choosing a different version.
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 "Previewing and finalizing your deployment" help article.
Important Notice on Restoring with Regenerated Tulip IDs
When regenerating Tulip IDs, be mindful that attempting to restore to a version prior to Tulip IDs regeneration may result in elements with newly generated Tulip 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 revert activities accordingly to make sure you recover the application connection's configuration.