Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt

Use this file to discover all available pages before exploring further.

When snapshots are enabled on your deployment, every save of a workflow auto-creates a versioned copy of its definition. Snapshots let you inspect what a workflow looked like at a previous version and restore the workflow to an older version if a recent edit broke something. The History panel must appear on the workflow detail page. If not, this deployment doesn’t have workflow snapshots enabled — contact your team admin.

​
When a snapshot is created

Snapshots are created automatically every time a workflow is saved in Cloud — there’s no explicit “create snapshot” button. The version number on each snapshot reflects the order of saves.

​
View history

  1. Open the workflow’s detail page.
  2. Click Show history (or the equivalent label in your deployment).
  3. The panel lists the most-recent 50 snapshots with version badge, runtime type, optional note, and creation date.

​
Preview a snapshot

Click Preview on a snapshot to open a modal with:
  • The full workflow JSON at that version.
  • The parameters table (key, type, default, whether required).
Previewing is read-only — it doesn’t change the live workflow.

​
Restore

Click Restore on a snapshot. Cloud asks for confirmation, then overwrites the live workflow with the snapshot’s definition. The old live version is itself preserved as a new snapshot, so you can always restore back. Tasks already in flight are not affected — they carry the parameters they were submitted with. Future dispatches use the restored version.

​
How long are snapshots kept

The history panel loads up to 50 most-recent snapshots in one request. Snapshots beyond that are still retained on the platform but not surfaced in the UI. Contact your team admin if you need an older version that’s not visible.
  • Workflows — concept.
  • Tasks — what’s affected (and what isn’t) by a restore.