Versions

Go back to an earlier setup of your workflow, and undo your own memory changes. Automatic versions are removed after a set number of days; a workflow keeps only your most recent saved versions.

Versions are saved copies of a workflow's setup: its neurons and their settings, its connections, and its notes and layout. Use them to look back at how a workflow was set up, or to restore an earlier setup after a change that didn't work out. The same section also lists the memory changes you made, so you can undo them.

The Versions section

Open Versions in the canvas's left rail.

Current at the top is the workflow as it is now. It shows Saved, or "Saving changes…" while your latest edit is being saved, and "published" when the workflow is published as an agent.
Below it is the History, newest first. It lists two kinds of rows, side by side in time order:
- Versions. Each shows its number (v1, v2, …), a label that describes the changes, when it was kept, and how long it is kept: "automatic · removed on" a date, "saved by you · kept among the last" followed by how many are kept, or "published · kept until deleted". Each has Restore and Delete, and you can click the row to look at it.
- Memory changes you made. For example "You edited “Pricing notes”". Each has Undo, and Redo after you undo it. See Undo your memory changes below.
Show older loads more rows when there are many.
Storage used shows how much of this workflow's storage is in use, as a percentage. Versions and your memory changes count toward it, along with the workflow's Docs and dashboards.

Versions kept for you

A version is kept automatically:

when you create the workflow (Starting point),
when you come back to edit after a break,
when you make a bigger change, such as adding or removing a neuron, changing a connection, or changing what a neuron makes or where it sends. The version holds the workflow as it was just before the change, and its label says what is about to change, for example "Before adding" followed by the neurons being added. At most one is kept every few minutes, so several bigger changes in a row share one version. Moving neurons around never adds a version,
when you publish the workflow as an agent,
when you restore an earlier version (named, for example, "Restored v1").

How long versions are kept

Automatic versions are removed after 7 days. A workflow keeps at most the last 25 versions automatic versions; when a new one is kept beyond that, the oldest automatic version goes first. Every row says the day it will be removed.
A workflow keeps the last 5 versions you save yourself. They are never removed for age. When you save one more, the oldest saved version is removed to make room, and you are told so. Delete a saved version yourself if you want to choose which one goes.
A version kept when you publish as an agent ("Published as an agent") is kept until you delete it, because it records what you shipped.
Your memory changes in the list are kept for 7 days too, and at most the last 25 changes of them.

If every automatic version has expired, the next edit after a break keeps a new one, so the list is never left without a recent one. "Starting point" is an automatic version too, so it is removed after 7 days as well. Save a version if you want to keep that setup.

Save a version yourself

Save a version before a big change, so you can go back to it. A workflow keeps the last 5 versions you save: saving another removes the oldest saved version, and the section tells you when that happens ("Saved. The oldest saved version was removed").

In the Versions section, click Save version.
Optionally type a name, for example "Before new pricing prompt", up to 120 characters. Without one, it is called "Saved version".
Click Save.

If the workflow's storage is full, the version isn't saved and the section says "Not saved: this workflow's storage would go over" the limit. Click Open storage in Docs, free some space, then save again.

Delete a version

Click Delete on a version, then Yes, delete to confirm. A deleted version can't be brought back. Use this to remove a saved version you no longer need (to choose which one goes before the oldest is removed), or to free storage: you can delete automatic versions too.

Look at an older version

Click a version in the list. The canvas shows that version.
The section reads Viewing plus the version's number, and the top bar shows Older version. Nothing can be changed or run while you look.
Click Back to current to return to the workflow as it is now.

Restore a version

Restoring makes an older version the current setup.

Click Restore on a version in the list, or Restore this version while you are looking at it.
The restore is added to the list as a new version, for example "Restored v1", and becomes the current setup.

Restoring brings back the setup only. Your memory changes stay as they are, and you undo them one by one in the list.

If you changed anything since the last version, those changes are kept as a version first, so you can restore them again if you change your mind. That version is named "Before restoring v3" (with the number of the version you restored). If you only moved things around on the canvas since the last version, no extra version is kept. Each neuron's last result stays as it is now: versions hold the setup, not the results. Undo and redo for canvas edits start fresh after a restore; undo for your memory changes made in this tab stays.

Undo your memory changes

Undo is for your own edits only. The list shows the memory changes you made yourself: creating or editing a memory, setting it to Don't use or Use again, changing Keep it, replacing a file, deleting a memory, and saving a suggestion in Review. Changes a run makes (Remember) are never listed here and can't be undone from the list.

Click Undo on a row to reverse that change, and Redo to apply it again, until something else changes the memory. If the memory was changed again later, the row says "Changed since. Undo the later change first."
A change can be undone for 7 days. After that it is removed from the list.
A memory you delete can be restored with Undo for 7 days. After that it is deleted for good, with its content, its files and its history, and the space it used is freed. A memory that expired (including an Auto memory removed after 7 days without use), or that a run removed, can't be restored: add it again in Memory.
Ctrl+Z (Cmd+Z on a Mac) also steps back through the memory changes you made in this browser tab, together with your canvas edits, in the order you made them. Ctrl+Shift+Z (Shift+Cmd+Z) or Ctrl+Y steps forward. While you are typing in a text box, it first undoes the text you typed there; when the box has nothing left to undo, the next press steps back through your changes. Older changes, and changes from other tabs, are undone from the list.
If the storage is full when you change a memory, the change is saved but can't be undone, and you are told so.

Storage

Versions and your memory changes count toward the same storage as the workflow's Docs and dashboards: up to 50 MB per workflow, and 500 MB across all your workflows. A document's own revision history doesn't count; versions do. The Storage used bar in this section and in Docs shows the same figure.

When the storage is full:

A version you save is refused, with a message.
Automatic versions first remove the workflow's oldest automatic versions to make room. If that isn't enough, they pause, and the section says "Automatic versions are paused: this workflow's storage is full." Your edits are still saved. Delete versions, documents or files to free space.
A memory change is saved but can't be undone, and deleting a memory is refused until there is room.

Two versions saved at the very same moment can together go slightly over the limit.

What a version doesn't hold

A version holds the workflow's setup on the canvas. It keeps the name of a file you added to a neuron's GET, but not the file itself. If that file has been removed since, the restored setup shows its name in red with a line through it and the note "File missing"; add the file again. Memory, the workflow's Docs and each neuron's last result are not part of a version, and restoring a version doesn't change them. Your own memory changes are listed next to the versions, with their own Undo; see Undo your memory changes and Memory.

Limits

Version name: up to 120 characters. You can't type more than that.
Automatic versions kept: the last 25 versions of each workflow, for up to 7 days. Versions kept on publish are kept until you delete them.
Saved versions kept: the last 5 versions of each workflow. Saving another removes the oldest saved version.
Memory changes you can undo: the last 25 changes, for up to 7 days.
Storage: up to 50 MB per workflow and 500 MB across all your workflows, shared with Docs and dashboards.

Common problems

Restore is greyed out

The workflow is published as an agent, and a published workflow can't be changed. Unpublish it first (open the listing button in the top bar, for example Public on Store, and choose Unpublish to edit), restore the version, then publish again. See Publishing your agent.

I can't edit or run anything

You are looking at an older version. Click Back to current in the Versions section.

A version I expected isn't there

Versions are kept after a break in editing, before a bigger change, on publish and on restore, not after every change. Automatic versions are removed after 7 days, and a workflow keeps only its last 25 versions. Click Save version whenever you want a copy you can come back to: a version you save is kept until it is one of the oldest beyond your last 5 versions, so save one you want to keep and delete the ones you don't need.

Not saved: storage would go over the limit

The workflow's storage is full, and versions count toward it. Delete versions you no longer need, or documents and files in Docs, then save again.

Automatic versions are paused

The workflow's storage is full, so automatic versions can't be kept right now. Your edits are still saved. Delete versions, documents or files to free space; automatic versions start again on their own.

A memory change can't be undone

The row says why: it was changed again later ("Changed since. Undo the later change first."), or it is older than 7 days. Changes made by a run are not listed and can't be undone from here.