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

# Version Control

Learn how modifying an Automation creates restorable versions

Every change made to a workflow creates a new version. Previous versions can be viewed and restored, giving you a safe fallback when updating an automation.

## Viewing workflow versions

To view previous versions, open the automation and select the **Versions** tab.

Versions are listed with the most recent first. Each version shows:

* The version number
* When the version was created
* The user who created it
* The workflow name

Hover over a version and click **View** to see a snapshot of the workflow at that point in time.

## Restoring a previous version

To restore an older version, locate the version you want to use.

You can roll back to it in either of the following ways:

* Open the version using **View**, then click **Rollback**
* Click the three-dot menu beside the version and select **Rollback**

Rolling back restores that version of the workflow so you can recover from unwanted changes or return to a previously working configuration.


---

# 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.couchdrop.io/automations/overview/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.