---
title: "Automations versions"
slug: "automations-versions"
updated: 2023-06-21T20:17:00Z
published: 2023-06-21T20:17:00Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations versions

*Learn about Versions and how to use them within the Automations feature.*

## What are Versions?

Much like how apps have Development Version and Published Versions, so do Automations. Versions are created each time you publish a development version, or a new iteration of an automation. With versions, you can archive previous automations and update them with a new process. Each version saves for your record, in case you need to revert back to a previous one.

A development version is a newly created or edited version of an automation.

A published version is a newly published automation, which can replace the previous one in production should you choose to.

          NOTE

          

All previously published versions of the current automation are read-only.

## How to Use Versions

Having versions allows you to develop or improve an existing automation without it immediately starting to Run. An existing automation can keep running while you are building the next version. With versions, you have control over when to publish the next version for implementation control.

## Version History Page Overview

![Automations Version History Page](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Version%20History%20Page.png)

To navigate to the versions page, select an automation from the **Automations page**. You will automatically route to the version history page, but if not, you can click the **Version History** tab at the top.

The version history page contains information about each individual automation’s version. The left column shows the version number. The center column details the published version information, including the user and the date and time of publication. If you want to edit the automation and create a new version, click the **Edit** button in the top right of the page or **Development** under the version number.

![Automations Version History Page](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Version%20History%20Page.png)

## Further Reading

- [Getting Started with Automations](/r230/docs/getting-started-with-automations)
- [Overview of the Automations Editor](/r230/docs/overview-of-the-automations-editor)
- [How to Use Automations Run History](/r230/docs/how-to-use-automations-run-history)

**Development Version**

The **Dev Version**of a Tulip app is the work-in-progress of your application after an app has been published. If a **Station**is assigned to run the Development version of an application, it will see live changes as they are made in the app editor.

Generally, **Stations**running in production will be running the **Published Version**of an Application.

**PublishedVersion**

The **Published****Version**of a Tulip app is a complete version of your Application. When an app is ready to be run in production, its logic can be *frozen*by Publishing that app. One application can have multiple published versions. If a **Station**is assigned to run the Published version of an application, it will only see changes when they are published.

**Automation**

**Workflow** that performs tasks in the background, without an interface. Automations run logic every time an **event** occurs.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations1.gif)

**Run**

Occurs each time an event is invoked in an **automation**.