Create checkpoints and restore versions

Use a named checkpoint when you need to identify a meaningful graph state later. An ordinary Save protects your current work; the checkpoint adds a recognizable history entry. This guide uses a threshold change from 55 to 60 as an example. You need an editable strategy and checkpoint availability for your account.

Create a checkpoint

1. Open the current editable strategy and check that the graph is valid for saving. Keep the editor open if it reports Offline, Error, or Conflict.
2. Save the current graph and wait for Saved.
3. Choose Save checkpoint in the toolbar. Enter a distinct label such as RSI 55 baseline.
4. Read the retention preview. If it names an older checkpoint that would be pruned, decide whether this new checkpoint is worth replacing it before confirming.
5. Confirm and wait for success. Then open version history and find the named entry.

Checkpoint retention and availability can depend on your plan. A duplicate label or a stale/conflicting version can prevent creation; read the dialog error, resolve it, and retry only after the current graph state is clear. Now you can change Condition's literal threshold to 60, update the Alert text to match, validate, and save. The checkpoint still identifies the 55 state for as long as retention keeps it.

Preview a version

Open the version selector in the editor or the Versions tab on strategy details. Choose a named checkpoint; use the search and paginated history when needed. An exact historical editor preview is read-only: inspect Condition and Alert, but do not expect typing, autosave, or Backtest launch to modify that snapshot. The main graph with threshold 60 is unchanged merely by previewing the old 55 version.

Use Return to Main when you only needed to inspect the older state. If preview is blocked, first resolve dirty, saving, offline, or conflict state in the current editor rather than forcing a page reload.

Try it here

Preview and restore a checkpoint

Create a named recovery point, preview history safely, and restore without deleting older versions.

Exercise steps

1. Create a local checkpoint, then change the graph.
2. Preview the checkpoint read-only and restore it while retaining the previous exercise version.

Start lesson

Restore a version

Go to the strategy detail page, open Versions, and choose Restore on the entry that represents the desired state, if that action is enabled. Review the confirmation and any named retention impact; cancel if you are unsure which version will become current. The historical editor preview itself is for inspection and does not provide the restore action.

After a successful restore, open Edit in editor for the current strategy and check the actual threshold, Alert message, and connections. The restored content becomes a new current version with restore provenance; the operation does not rerun past Backtests. If the restored configuration is not what you intended, inspect history again and choose the correct available version rather than editing the historical preview.