> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/environments-releases-and-version-control.md).

# Version History and recovery

Choose the recovery method that matches the change. App history, environment backups, and database recovery have different scopes.

| Need                                             | Start here                                                                                                                                               |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Inspect or preview recorded app changes          | [Version History](/ai-app-builder/test-and-publish/version-history.md)                                                                                   |
| Return to a recorded app state                   | Version History → the selected version's menu → Revert version                                                                                           |
| Download or restore an environment configuration | [Environment settings](/jet-bridge-deployment/environments.md)                                                                                           |
| Transfer a backup between Cloud and On-Premise   | [Cross-Instance Backup & Restore](/jet-bridge-deployment/environments-releases-and-version-control/version-control/cross-instance-backup-and-restore.md) |
| Use the earlier snapshot/release interface       | [Version Control](/jet-bridge-deployment/environments-releases-and-version-control/version-control.md)                                                   |
| Recover records or external effects              | The affected database, API, or workflow's recovery process                                                                                               |

## Review a version before reverting

Open the history icon beside **Publish**, select an entry, and use **Preview version** or **Show changes**. Confirm the version label and review the affected behavior before choosing **Revert version**.

![Version History with dated entries and a selected version marked Previewing now](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FN9U4JoGiFvwcZ0RJAzpI%2Fversion-history.png?alt=media)

Follow the canonical [Version History guide](/ai-app-builder/test-and-publish/version-history.md) for the complete workflow.

## Prepare an environment backup

Open the app menu, select the gear beside the intended environment, and use **Download backup**. Record the app, environment, date, and platform version with the file.

Before using **Restore backup**, verify the target environment and the backup you intend to apply. Review the configuration and rerun [release checks](/jet-bridge-deployment/publish-your-app/verify-a-release.md) afterwards.

App or environment restoration does not establish that connected records or external workflow effects were reversed. Identify those systems separately and confirm their recovery scope.

## Keep a release record

Record the approved app version, environment, platform version, backup location, and verification results. Use that record to compare the last working state with an incident, and repeat affected permission and data tests after recovery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/jet-bridge-deployment/environments-releases-and-version-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.