Workflow Versioning

NodeLoom automatically creates a new version every time you save a workflow. This gives you a complete history of changes, the ability to compare versions side by side, and the safety of instant rollback.

Automatic versioning

Versions are created automatically. Every save creates a new version. You do not need to manually create or name versions.

Overview

Each workflow maintains a version history of up to 50 versions. When the limit is reached, the oldest version is automatically removed as new versions are created. Each version captures the complete workflow state including all nodes, edges, configurations, and metadata.

PropertyDescription
Version NumberAuto-incrementing integer starting at 1. Displayed in the version history panel.
TimestampThe date and time the version was created (when the workflow was saved).
AuthorThe user who saved the workflow, creating this version.
SnapshotComplete workflow definition including all nodes, edges, and their configurations.

Version History

Access the version history panel from the workflow editor toolbar. The panel shows all saved versions in reverse chronological order (newest first). For each version you can:

  • Preview the version to see the workflow canvas as it looked at that point in time.
  • Compare two versions side by side to see which nodes, edges, or configurations changed between them.
  • Restore a previous version to make it the current active workflow. Restoring creates a new version (preserving the full history).

Version Evaluation (A/B Testing)

Version Evaluation lets you compare two workflow versions by running both against the same set of test inputs. This is useful for validating that changes to prompts, parameters, or logic produce better (or equivalent) results before promoting the new version.

StepDescription
1. Select versionsChoose two versions to compare (e.g. the current production version and a candidate version).
2. Provide test inputsSupply a set of test inputs that both versions will process. You can enter inputs manually or load them from previous execution history.
3. Run evaluationBoth versions execute against every test input. Executions run in parallel for speed.
4. Compare resultsView outputs side by side for each test input. Differences are highlighted, making it easy to spot changes in behavior.

Non-destructive

Version evaluations run in an isolated context. They do not affect the active workflow, trigger production side effects, or modify any data. External API calls are still made, so use test credentials or sandbox APIs when evaluating workflows that call third-party services.

Rollback

To restore a previous version, select it in the version history panel and click Restore. This creates a new version with the same configuration as the selected version, so no history is lost. The restored version immediately becomes the active workflow definition.

If the workflow is deployed in multiple environments, restoring a version only affects the Development environment. To update Staging or Production, promote the restored version through the normal environment lifecycle.