Going back
Restoring an earlier version when a change turned out to be wrong.
Every build is kept, so going back is always possible.
Find the version#
The Versions tab lists them newest first, each named after what was asked for. If you named one yourself, it stands out from the automatic entries.
Look for the name of the change you want to undo, and take the version before it.
Two different kinds of going back#
Something is wrong on live or test. Deploy the earlier version into that environment. Press Put live or Send to test on it. In a minute or two the environment is serving the old version again, with its data intact.
This is the fast fix, and it is the one to reach for when customers are affected. It does not touch the preview or the conversation.
The working copy has gone wrong. You want the preview itself back to an earlier point, so that the next build starts from there. Press Go back to this on the version you want.
Going back in the workbench#
Go back to this, on any version in the list, puts the working copy back to how it was at that point. The preview restarts showing it, and the next thing you ask for carries on from there.
Nothing that is deployed changes. Live and test go on serving exactly what they were serving. That is deliberate: people are using the live application, and it must not change because somebody was reading through the history. When you are happy with what you have gone back to, deploy it like any other version.
It is itself undoable. Whatever was in the workbench is saved as a version first, so going back to last Tuesday leaves everything since last Tuesday in the list, and you can go forward again by pressing Go back to this on it. You cannot lose work this way, including work you had not thought to save.
Asking instead#
Often simpler than finding a version, especially for a recent change:
Undo the last change.
Put the proposals list back the way it was this morning.
The whole conversation is still in context, so this morning is something it can resolve.
The data does not go back#
Restoring a version restores the code. It does not restore the database.
If the earlier version expects fields that a later one removed, or the other way round, say so:
Go back to the version before the merge, and keep the notes people have added since.
Nothing is deleted by going back#
Neither deploying an old version nor going back to one removes the newer ones. They are all still there, and you can go forward again just as easily.