---
title: "Versions, restore and upgrades - Workflow Suite"
description: "Every save of a workflow is a version you can restore. And when an action or trigger gets a newer version, the editor tells you and upgrades on request."
canonical: "https://docs.workflow-suite.app/versions-and-restore"
---

# Versions, restore and newer versions of actions

Two kinds of versions keep your workflows safe: the versions of **your workflow**, which you can restore, and the versions of **our actions and triggers**, which change without breaking what you built.

## Versions of your workflow

Every save that changes the trigger or the steps is kept as a version.

### Look at a version and restore it

1. Select **Versions** in the toolbar above the canvas. **Version history** opens.
2. Pick a version from the list. The preview shows what started the workflow then (**Starts when**) and its steps. The version in use is marked **Current**.
3. Select **Restore this version**, then confirm with **Yes, restore**.

The steps on screen, including unsaved changes, are replaced by that version. Restoring writes a **new** version, so nothing is lost: you can always go back to where you were.

### Undo and redo

While you edit, the undo and redo arrows in the toolbar step back and forth through your changes, including deleted steps. Undo works until you leave the editor; versions last.

### Runs keep their version

A run uses the version that was current when it started. A run that waits for days at a **Wait** step continues with the workflow as it was, even if you saved changes in the meantime. New runs use the new version.

### Deleting a workflow

Deleting a workflow permanently deletes its version history too. Runs that are waiting are not continued. The run history is kept. This cannot be undone.

To keep a copy before a big change, use **Duplicate**. The copy is turned off, and a copy of a workflow with an incoming webhook gets its own URL.

## Newer versions of actions and triggers

We improve ready-made actions and triggers over time. There are two kinds of change:

- **A compatible change** ships for every workflow without notice: a fix, a new optional field, a new value in the result. Nothing is removed or renamed, so your workflow keeps working as it is.
- **A breaking change** becomes a **new** action or trigger. The old one stays, keeps running for the workflows that use it, and is no longer offered in the pickers.

### The upgrade hint

When a part of your workflow has a newer version, the editor shows a banner: **A newer version is available for one part of this workflow**. Select the part. Its panel says **A newer version of this action is available**, with one sentence on what is different.

1. Read what changes.
2. Select the upgrade button. The step moves to the new version. Values of fields that still exist are kept.
3. Check the fields and run a **Test**.
4. Save. **Undo** brings the old version back if you change your mind before saving; afterwards, **Versions** does.

You can also upgrade all parts at once from the banner, and test before you save.

### When an old version ends

Usually there is no deadline: the old version keeps working as it is. Only when Shopify itself retires what an action or trigger is built on, the hint names the day: **This version stops working on** that date. Upgrade before that day, then test the workflow.

### Shopify Admin API versions

Steps that call the Shopify Admin API directly use the API version chosen for the workflow. Shopify retires old API versions on its own schedule. The step's docs box warns when a mutation or query is deprecated or does not exist in the chosen version. See [Every Shopify mutation and query](https://docs.workflow-suite.app/shopify-mutations-and-queries.md).

## Over the Developer API

Versions can be listed and restored, and a workflow's available upgrades can be read and applied over the API. See [Developer API and MCP](https://docs.workflow-suite.app/developer-api-and-mcp.md).

## Related

- [Test, preview and debug](https://docs.workflow-suite.app/test-preview-and-debug.md)
- [How a workflow runs: triggers, steps and runs](https://docs.workflow-suite.app/how-a-workflow-runs.md)