Revision History
Every time you save a strategy or super-node, the platform records a snapshot. You can browse the history, compare versions, and restore any earlier state without losing anything.
Cosa Imparerai
- ▸How the automatic snapshot system works
- ▸How to access revision history from the strategy editor
- ▸What restore does — and why it's non-destructive
- ▸How the same system applies to super-node templates
What gets saved#
Every save of a strategy or super-node template creates a new revision — a complete snapshot of the definition at that moment. Revisions are numbered sequentially (1, 2, 3 ...) and stored with the timestamp and the name of the user or session that triggered the save.
The revision system covers **strategies** and **super-node templates**. Both follow the same behavior.
Why this matters#
Save often and save freely. Every state is recoverable. If you spend an afternoon restructuring a strategy and decide the new version is worse, you can go back to any earlier point — the one right before you started, or any intermediate state along the way.
There is no penalty for saving frequently. More saves means more checkpoints.
How to access revision history#
From the strategy editor top bar, click the **History** button (clock icon). A modal opens showing the full list of revisions for the current strategy.
The left column of the modal lists revisions in reverse chronological order — most recent first. Each row shows the revision number, timestamp, and who saved it.
Click a revision to preview it on the right side. The diff view shows which nodes and edges were added, removed, or modified compared to the current version.
Restoring a revision#
Select the revision you want in the list, then click **Restore**. The platform takes a two-step confirmation before applying the change.
Restoring is **non-destructive**. The platform does not overwrite the current version. Instead, it creates a new revision that contains the restored state. Your current version is preserved as the revision immediately before the restore.
If your strategy is at revision 7, restoring revision 3 creates revision 8, which is identical to revision 3. You can still return to revisions 4, 5, 6, and 7 at any time.
A practical example#
- Rev 1 You build version 1 of an RSI strategy and save it. Revision 1 is created.
- Rev 2 You add a MACD confirmation filter and save again. Revision 2.
- Rev 3–4 You change the exit conditions and save twice more while tweaking. Revisions 3 and 4.
- Restore The MACD-filtered version backtests worse than the original. You open History, select revision 1, preview the diff, and confirm the restore.
- Rev 5 Revision 5 is created — identical to revision 1. You continue building from this checkpoint. Revisions 2, 3, and 4 are still accessible.
Super-node revisions#
The same system applies to super-node templates. The **History** button is available in the super-node editor. Every save creates a revision. Restoring a super-node revision creates a new revision of that template.
Note: If a super-node template is used inside a strategy, the strategy's behavior at runtime reflects the current state of the template. Restoring the template creates a new revision but does not automatically update existing strategies that reference it — those continue using whatever state they were saved with.