Database
Restore your app's data to an earlier time
Put the published app's data back to how it was at any minute in the last 30 days, and undo the restore if you need to.
On this page
Ahamo keeps the published app's data restorable to any minute in the last 30 days. A restore puts the data back to how it was at the time you choose; everything saved after that is undone, and you can undo the restore itself. It is self-service for every published app.
When to use it
- Someone deleted or overwrote records by mistake.
- A faulty change in the app saved wrong values, and you want the data from before it.
A restore changes data, not the app. To undo a build, use history and undo. Restores act on the published app's data only; development data is not restored.
How to restore
- Open Runtime › Data and find Backups.
- In Restore to, choose the date and time. It starts at one hour ago.
- Select Preview restore and read the dialog, which names the data that goes back and the time.
- Confirm.
Restoring shows while it runs, then Restored to and the time. Saving in the app pauses for a few seconds; people who try to save meanwhile are asked to try again in a minute. You can leave the page.
A restore does not touch sign-ins or uploaded files, which stay as they are.
Undo a restore
Select Undo restore on the Backups card and confirm. The data goes back to how it was just before the restore, and anything saved since the restore is undone too. You can undo the last restore within 30 days, as long as no publish has changed the database since. An undo cannot itself be undone.
Apps on your own Postgres
When the app's data is in your own Postgres or your Supabase project, your database provider keeps the backups and the card links to them. Export now downloads the app's tables and data as one SQL file. See Export your app's data.
Plans and limits
Restores work the same on every plan.
| Rule | Value |
|---|---|
| Oldest point you can restore to | 30 days ago, and never before the last publish that changed the database |
| Newest point | 1 minute ago |
| What is restored | Data the app shares between its users; data kept separately per owner is not restored |
| Longest pause in saving | 10 minutes; after that the restore stops and saving resumes |
| At the same time | One restore, database move or publish at a time |
Viewing the card needs read access to the app's database. Restoring, undoing and exporting need permission to publish the app.
Troubleshooting
The time is refused as before the last publish. A publish changed the database's structure after that time, so the app could not read the older data. Choose a later time.
"The restore stopped" or "Restore stopped part way". Some data is restored and some is not. Select Retry to continue from where it stopped, or Undo restore to go back. The app's Overview shows a banner until you do.
Publishing says the data is being restored. Wait until the restore finishes, then publish again.
The preview is out of date. The app's data changed since you previewed; select Preview restore again.