Every time your site is published — after a generation, an edit, or a repair — A3 iFrame records a release. The release history is your safety net: a numbered log of every published version of your site, with the ability to put an earlier one back live.
Finding it
Open a site from your dashboard and go to its release history, listed under Site History → Releases. Releases are numbered in order with the newest first, and the version currently serving visitors is marked as the current one.
What each release tells you
- Its number — releases count up, so #7 came after #6.
- Whether it's live — exactly one release is current at any time.
- Build status — whether that version built and published successfully.
- Build time — when it started and finished.
- Its address — the public link for that version.
Restoring an earlier release
If a change didn't work out, choose an earlier release and restore it. That version becomes the live one again and visitors see it straight away. Restoring doesn't delete anything — the release you were on stays in the list, so you can move back and forward as you like.
This is usually the fastest fix when an edit or a repair produced something you don't want. It's quicker and far more predictable than regenerating and hoping for a similar design.
When it's especially useful
- After a content edit that turned out worse than what you had.
- After a repair that fixed one thing but changed something else.
- When you want to compare two versions before settling on one.
Failed builds never go live
If a publish fails to build, the version you were already serving stays up — a broken build is never promoted to your visitors. That means the list can contain releases that never went live, and seeing one is normal rather than a sign of a problem.
If your site has no releases yet, publish it once and the first one appears. If a restore won't complete, open a ticket from support with the site name and the release number you want back.