Version History and Rollback

View previous versions of your workflow and restore them if needed.

Overview

Every save creates a new version of your workflow. Spojit keeps the full history so you can compare what changed, see who changed it and when, and restore a previous version when a recent edit causes a regression.

Versioning is automatic and you do not need to opt in. It covers both the canvas (nodes and edges) and per-node configuration. Rollback never destroys history: restoring an old version creates a new version on top, so the change is itself reversible.

How Versioning Works

A new version is created each time you click Save in the designer.
Each version stores the full canvas and node configuration at that point in time.
Each version records the timestamp and the member who saved it.
Settings changes (name, description, folder, notifications) are versioned alongside the canvas.

Viewing Version History

Open the workflow in the designer.
Click the Version History icon in the toolbar.
Browse the list of versions. Each entry shows the timestamp and the member who saved it.
Click a version to preview its canvas without restoring.

Restoring a Version

In the version history panel, select the version you want to restore.
Click Restore. The canvas updates to show that version.
Review the canvas to confirm it is what you want.
Click Save to commit the restored version as the new current version.

Tips

Save often. Each save is a checkpoint you can roll back to.
Before a risky edit, save a clean version first so the rollback target is obvious.
Use the timestamp and member columns to find the version "just before X happened".

Common Pitfalls

Restoring a version is not committed until you click Save after restore. Closing the designer first abandons the rollback.
In-flight executions continue with the version they started on. Rollback only affects new runs.
Connection credentials are not versioned. Restoring an old version still uses today's credentials.
Restore creates a new version entry rather than replacing history, which is intentional - it keeps the audit trail intact.