RunComfy’s workflow versioning lets you iterate on ComfyUI workflows, including those modified from community templates, with built-in safeguards for reproducibility and stability. This allows you to focus on enhancing your workflow’s generative features without worrying about regressions or breaking deployments.

​
Saving a New Version

To create a new version, launch an existing workflow into a ComfyUI session and make your updates. Then click Cloud Save in the top bar, keeping the same workflow name. RunComfy will automatically increment the version number and package the updated graph along with its complete runtime environment (drivers, libraries, custom nodes, models, and dependencies) into a new container image. Each version is fully independent with its own isolated environment, ensuring it can be restored exactly as saved. A single workflow can have multiple versions, making it ideal for managing feature tests, variations, or rollbacks.

​
Accessing Versions

On the My Workflows page, find your workflow, click the three-dot icon, and select More Versions to view its full history. From there, choose any version to launch it in a ComfyUI session for review, further edits, or deployment preparation.

​
Versioning in Deployments

Deployments are tied to a specific workflow version, so new versions don’t impact running endpoints. They continue using the original version for uninterrupted operation. Test new versions thoroughly in isolation to catch issues, then switch via the deployment settings (as detailed in Edit a Deployment). Updates roll out seamlessly with minimal downtime—similar to a rolling deployment—ensuring no disruption to live API traffic.