Undoing a change

The points save themselves

You do not have to remember to save. Every job that finishes successfully leaves a point behind, automatically.

The list is in order, newest first. Name the ones that matter so you can find them later.

Going back

Pick a point and restore it. Your files go back to how they were then, and the preview is built again from that version.

It takes about as long as a small build, because it really is one.

When to reach for it

The common case is simple: you changed something and it got worse. Going back one step beats trying to talk your way out of it.

The same goes for a page that came out blank, or a button that used to work and now does not. Return to the version that worked and start again from there.

You can undo the undo

Before restoring anything, the current state is saved as a point of its own.

So going back is never a one-way door. Restore an old version, decide you preferred the new one, and go forward again.

What comes back

The code and the screens come back for certain. Whether the data that visitors entered comes back too depends on the point you picked.

The screen says which kind it is before you press. Read that line — it is the difference between getting orders back and not.

What you already published stays where it is. Restoring changes your preview first; what customers see changes when you publish again.

It does not cost credits

Restoring is free, however many times you do it. We are not going to charge you for undoing something.

So use it. Trying a bold change is cheap when getting back costs nothing.