What is live
Each publication is a deployment. The app’s Dashboard shows the Live deployment: which version is being served, and what it was built and verified with.
Deployment history
Deployment history lists what the app has served, newest first, including rollbacks and the reason given for each.
Serve an earlier deployment again
If something breaks after a publish, select Serve this again beside an earlier deployment, say why you are rolling back, and confirm. Atomic checks the stored release and serves it in place of the current one. Nothing is generated or rebuilt, and it carries on if you close the page.
- Your source does not change, and the deployment you replaced stays in the history.
- Your app’s data is untouched: the people, records and files it has collected stay exactly as they are.
- An earlier deployment can be served only if it works with the app’s data as it is now. A published change to how data is stored is not undone.
- Only the owner or an admin can roll back.
Rolling back is not restoring a version
Rolling back changes what visitors get, straight away, from releases already built. Restoring a version changes the source you are building on, and reaches visitors only when you publish again.
Activity
The app’s settings also keep a record of who did what to the app, newest first, including actions that were refused. It is kept for a fixed period and outlives the app.