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

# Workflow Versions

RunComfy workflow versioning lets you iterate on ComfyUI workflows while keeping deployments stable and reproducible.

Each time you **Cloud Save** a workflow, RunComfy creates a new **immutable version** (a packaged snapshot of the graph + runtime environment). Deployments can then be pinned to a specific version, and upgrades are explicit.

***

## Save a new version

To create a new version:

1. Launch an existing workflow into a ComfyUI session.
2. Make your updates (nodes, models, parameters, etc.).
3. Click **Cloud Save** in the top bar **using the same workflow name**.

RunComfy automatically increments the version number and packages the updated graph along with its complete runtime environment (drivers, libraries, custom nodes, models, and dependencies) into a new container image.

***

## Version limits and auto-cleanup

Each workflow keeps up to **3 saved versions**.

When you save a new version:

* the oldest **non-deployed** version is removed automatically to stay within the limit
* versions currently used by a Serverless API deployment are protected and will not be auto-removed

***

## View and launch versions

Go to **[My Workflows](https://www.runcomfy.com/comfyui-workflows/my-workflows)**, open the three-dot menu, and select **More Versions** to see the version history.

You can launch any version into a ComfyUI session to review, edit, or prepare it for deployment.

***

## Deployments and versions

Deployments are pinned to a specific workflow version. Creating new versions does **not** change running endpoints—deployments keep using their currently selected version for uninterrupted operation.

To roll out a new version:

1. test the new version in a ComfyUI session
2. update the deployment to point to the new version (see **[Edit a Deployment](/serverless/edit-a-deployment)**)

Changes roll out with minimal downtime (similar to a rolling update) without disrupting live API traffic.