Go back to when it worked

What you need first

Nothing to set up. It helps to know roughly when it was still fine.

• Roughly when the app last worked the way you wanted.
• What you asked for just before it went wrong.
• A name on the versions you care about, so you can find them later.

01 · Find the version list

Every run that succeeds leaves a restore point. So does every save you make yourself in the code editor. They are listed newest first with what changed and how many files it touched.

02 · Decide whether restoring is the right move

If one section is wrong, asking again for that section is quicker. Restoring is for when several things broke at once, or when you cannot work out what caused it. Half an hour of hunting is usually worse than going back to a version that worked and asking again.

03 · Name the good ones

Bookmark and rename the versions that matter — “before I changed the prices”, “the one the client liked”. After twenty changes the timestamps all look the same, and that is exactly when you need to find one.

04 · Restore

Restoring puts the files back, reapplies the database structure from that point, and rebuilds the preview so what you see matches what you restored. No AI is called, so it costs 0 credits.

05 · Know that the undo is undoable

Your current state is saved as a restore point before the restore runs. If you go back too far, you can come forward again. Nothing is thrown away by going back.

06 · Check what came back

Click through the pages you were working on. The code and the shape of your data go back to that point. What customers have sent you since is your live data, not part of the version you restored.

If you get stuck

Which version was it? Each entry shows what the run was asked to do and how many files changed. Restore one, look, and if it is wrong restore another — going back and forth is free.

Will I lose my customers' bookings? Restoring is about your app, not about wiping what people have sent you. If a restore would change the shape of your tables, read what the screen tells you before confirming.

The restore did not finish. The result says which stage stopped rather than a single unhelpful failure. Stop editing and tell us what it says — carrying on from a half-restored state makes it harder to recover.