Help
Undo, and how history works
Undo returns your app to precisely how it was. It is not the builder reasoning about what it changed.
What happens on every change
Before your request runs, the state of your app is bookmarked. After it runs, the result is saved as its own point in history. Undo is a return to the bookmark.
That is why it is exact. Nothing has to work out what changed or reverse it step by step — the previous state is still there, whole.
What undo does not do
- It does not un-send anything your app already sent, or unwind a payment a customer made.
- It does not restore a file you deleted from your own computer.
- It does not refund the change. The work was done; you are undoing its result.
Going back several changes
Undo repeatedly, or ask for the state from a specific earlier point. Nothing is lost by going back — the later state does not vanish from history.
Why this matters more than it sounds
It is what makes experimenting free of consequence. You can ask for something odd, look at it, and put it back. Most of the best changes come from somebody who felt able to try.
Still stuck?
The support address and hours are on the contact page, and a person answers.
Access is by invitation and a person reads every request. The founder test is free, takes a few minutes, and tells you what you are getting before you commit to anything.