---
title: "Save a version and open an earlier one | Oplema"
description: "Save a named version, open an earlier one, return to your unsaved work, discard changes and understand automatic branches."
url: "https://oplema.com/docs/echo/saves"
updated: "2026-11-04"
---

# Saves

You need edit access to the project. All of this happens in the History tab.

## Save a version

1. Type a short description in What changed?.
2. Select Save or press Enter.
3. Your message appears as a new row at the top.

If the message is empty, Save does nothing. If nothing has changed since the last version, no version is added, but the typed message is cleared.

## Open an earlier version

1. Find the row you want. Select the row first if you want to [see how it differs](https://oplema.com/docs/echo/diffs).
2. Select Open on that row. The flow and dashboard load as they were.

Later versions stay in the list, each with its own Open button. Opening doesn't change or remove anything, except in the case under [Delete a branch](https://oplema.com/docs/echo/saves#delete).

If you had unsaved work, it's kept as a <current> row. Select Open on that row to return to it.

## Automatic branches

If you open an earlier version and then edit it, your work can no longer continue in a straight line. Oplema creates a new branch automatically, as soon as your edit autosaves, and gives it a name such as `uniform`. You'll see the new name as a colored tag and a second line in the list.

One saved version continued on two branches, each with its own colored tag

Your project now has two lines of work that don't join up again. There's no merge. To carry a change from one line to the other, make the change again by hand or ask Elara to. Use [Diffs](https://oplema.com/docs/echo/diffs) to see what differs.

## Discard unsaved work

Select Discard on the top row, the one marked unsaved. The project returns to the version you were on. There's no confirmation, and the discarded work doesn't stay in the list.

## Delete a branch

1. Select Open on the row with the branch's colored tag.
2. Select Options, then Delete entire branch.
3. Confirm the message "Delete this branch and all commits unique to it?"

Unsaved work on that branch is discarded with it. Versions that only that branch contains are gone from the list, and the editor moves to the nearest version that another branch shares. If no other branch shares a version, the project becomes empty, with a new Initial version.

Right after you delete a branch, select Open on the newest version of the other branch. If the editor lands in the middle of that branch and you edit there, its later versions stay listed only until you select Save or Open on one of them. Discard can also fail with "branch does not point at current changes: <branch>" and keep your work.

## Undo a change

To undo your last edit, press Ctrl+Z, or Cmd+Z on a Mac, with the cursor outside any text box. Shift+Ctrl+Z, Shift+Cmd+Z or Ctrl+Y redoes it. To restore or revert to an old, previous version instead, [open an earlier version](https://oplema.com/docs/echo/saves#open).

## Scope tags, schedules and publishing

- Detailed scope tags in Options shows finer tags on each row, such as `SL` for Strata logic or `VC` for Vista dashboard layout. Hover over a tag for its meaning.
- Schedules can run the latest version or a chosen one. See [Scheduling](https://oplema.com/docs/cloud/scheduling).
- Publishing can use a chosen saved version. See [Publish](https://oplema.com/docs/cloud/publish).

### Save your work. Go back any time.

Echo is Oplema's version history. Guest copies are deleted about 30 days after the guest session started.

[Try Echo in Oplema](https://oplema.com/editor?path=%2F%3Fopen%3Dstrata) [About Echo](https://oplema.com/echo)
