A snapshot is an automatic checkpoint you can restore if a change does not work.
When a snapshot is taken
Snapshots are created after successful changes to pages, functions, or Schedulers. Questions that do not change the app do not create snapshots.
Restoring a snapshot
-
Open snapshot history
Open the app chat and choose the history icon.
-
Choose a snapshot
Use the message preview to identify the working state you want. The current state is marked Current.
-
Restore it
Select another entry to restore it.
What a restore brings back
A restore replaces the app’s current structure with the snapshot’s:
- Pages, with their titles, paths, and code
- Functions, with their code and descriptions
- Schedulers, with their schedules, payloads, and enabled state
- Configuration keys and their values
- The app state at that point
What a restore does not touch
- Your Data records are not affected. Restoring does not undo records the app created, updated, or deleted. If a bad version wrote wrong rows, going back to the good version leaves those rows in place, and you have to correct them yourself.
- Anything the app did externally is not undone. Messages posted, spreadsheet rows written, and calendar events created stay where they are.
- Chat history stays as it is. The conversation is not rewound, only the app.
- App-level settings are not part of a snapshot. The app’s name and avatar, its Knowledge assignments, its connector assignments, and its connected agents are unchanged by a restore.
Recovering from an error
If an app reaches Error, choose Or, revert to last version to restore the most recent snapshot. Then request the change again in smaller parts.
Snapshots and manual page edits
A snapshot is a point in the app’s history you can restore. After restoring, test the app before continuing.
If you previously used the code editor to publish a page edit, restoring a snapshot does not publish that restored page state. Publish is optional and is only needed if you want to update that separately published version.