Workspace History, Snapshots, and Rollback
How the History tab works, what Save snapshot creates, what Restore changes, and how users should think about revisions, rollback, and persistence.
Workspace History, Snapshots, and Rollback
Where you see this in the app
This page explains the History tab inside the Workspace panel for a post you can edit.
The tab is meant for revision control from a user perspective: save progress, inspect older points in time, and restore a prior version when needed.
What Save snapshot does
The History tab says Each snapshot creates a git commit in the workspace.
For an end user, the important meaning is simple:
| Action | What it does |
|---|---|
Save snapshot | Records the current workspace state as a named history point. |
Refresh history | Reloads the current list of saved history entries. |
Restore | Reverts the workspace to the selected earlier history point. |
Treat a snapshot like a saved revision you can come back to.
Refresh history and commit list
Each history row shows:
| Field | What it tells you |
|---|---|
| Short ID | A short revision identifier for that saved state |
| Relative time | When the snapshot was created |
| Message | A brief description of the revision |
If the page says No commits found. Save a snapshot to create your first history entry., it means no saved revision exists yet for the current workspace state.
Restore vs save to storage
The History tab also warns:
Roll back to a previous commit to restore the project, then save a new snapshot if you want to persist it to storage.
The user-facing meaning is:
| Step | Why it matters |
|---|---|
Restore an older entry | Changes the active workspace back to that earlier state |
| Save again afterward | Makes the restored state your new recorded revision |
So Restore is not the same as publishing or sharing. It changes the working workspace state first. If you want that restored state to become the ongoing version you keep using, save a fresh snapshot after checking it.
When history feels empty or stuck
| Situation | What it usually means |
|---|---|
Loading history… never clears | The active workspace session may be stale or temporarily unavailable. |
No commits found | You have not created a snapshot yet in this workspace history. |
Rollback is only available in edit mode. | You are not in an editable workspace session. |
Workspace session not found or Workspace session token is missing | The current workspace session ended and needs to be relaunched. |
Recommended end-user workflow
- make a meaningful set of changes,
- click
Save snapshot, - test the preview or automation behavior,
- use
Restoreif the changes went in the wrong direction, - save another snapshot once the workspace is back in a good state.
This is the safest way to experiment without losing a known-good version.
Related docs
Related docs
See it in action
Previous
Workspace Manual Runs and Run History
How one-off manual runs differ from reusable rules, what queued or failed runs mean, and how to read the Runs tab when automation results look stuck or incomplete.
Next
Reply Workspace Clone Eligibility and Limits
How reply authors can clone a parent workspace into a reply, when that option appears, and which limits prevent cloning even if the parent post already has a workspace.