> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/18.latest/concepts/versioning.md).

# Versioning

Umbraco Automate uses the same draft and published model as Umbraco content. Every save creates an immutable version. Only the published version responds to triggers.

## Draft and Published

| State                   | What it means                                            |
| ----------------------- | -------------------------------------------------------- |
| **Draft**               | Your in-progress edits. Does not run when triggers fire. |
| **Published**           | The live version. Runs when triggers fire.               |
| **Unpublished changes** | The draft is ahead of the published version.             |

Editing a published automation creates a new draft. The live version keeps running until you publish your draft.

## Version History

The **Info** tab on an automation lists every version with its publish date and the user who published it. From the version list you can:

* **View** a previous version on the canvas.
* **Rollback** to a previous version. Rollback creates a new draft based on the chosen version.

<figure><img src="/files/QXfw233OuaQVtxjOpyHP" alt="The version history list on the Info tab of an automation."><figcaption><p>The version history of an automation.</p></figcaption></figure>

## In-Flight Runs

A run always completes on the version that was live when the run started. Publishing a new version, or rolling back, does not interrupt runs that are already in progress.

## See Also

* [Automations](/umbraco-automate/18.latest/concepts/automations.md)
* [Runs](/umbraco-automate/18.latest/concepts/runs.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-automate/18.latest/concepts/versioning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
