How to view scenario version history in Scenario Builder?
Scenario Builder is where you edit the bot scenario. Each time you publish changes, the system records a snapshot — a version. Each version includes:
- the state of all sections, nodes, and edges at the time of publish;
- date and time;
- author email (who published);
- an optional comment.
Version history lets you see how the scenario looked before, compare entries in the list, and make a chosen snapshot the current working state when needed.
When you need it
- You want to roll back after a mistake.
- You need to see who saved changes and when.
- You want to compare metadata for two entries side by side in the comparison panel.
Before you start
How to open version history
- Open the bot in Scenario Builder.
- On the toolbar, click the history icon (tooltip: Version history).
- A modal opens with the title Version history, showing saves from newest to oldest.
How to read the list
Each row shows:
| Field | Meaning |
|---|---|
| Version ID | Unique identifier (for support) |
| Date and time | When the save was created |
| Author | Email of the user who published |
| Comment | Change description, if provided |
| Current badge | The active scenario version |
A branch icon appears next to the ID. Scroll the list to load more entries automatically.
How to preview an older version on the canvas
- Click a row — it becomes selected.
- The right-hand panel shows a comparison (current vs selected).
- Click Preview — the editor opens that version’s graph (the URL includes a version preview parameter).
- To exit preview without applying changes, click Return to current version on the toolbar.
How to add or edit a version comment
Comments help your team understand what changed. You can add one when publishing or edit it later.
When publishing
- Click Publish on the toolbar.
- In the Publish Scenario dialog, fill in Version comment.
- Confirm publish.
After save
- Open Version history.
- Find the entry and use the comment (pencil) control to edit the description.
- Confirm with the check action.
Comparing two versions
For a selected entry, the modal compares metadata with the current version (date, author, comments). A full graph-level diff in one place may arrive in a future release.
Short, meaningful comments on each publish make history much easier to navigate.
How to make a selected version current
Caution: after you confirm, the current working scenario is replaced with the selected snapshot. Unsaved local edits may be lost — preview the graph first.
- In Version history, select an entry and click Preview to verify it is the right state.
- On the toolbar, click Publish (while viewing a history snapshot, the UI indicates you are in history preview mode).
- In the Confirm restoring the script version dialog, read the warning. Use Keep elements from the current version if that option is shown and you need it.
- Click Confirm to apply.
A new history entry is created after a successful operation, so you can roll forward again if needed.
FAQ
How many versions are kept?
Entries are not auto-deleted. For old bots the list can be very long — use comments and dates to find saves faster.
Can I delete a single version?
Per-entry deletion is not supported in the UI. For sensitive data issues, contact your instance administrator.
What happens to history when a bot is deleted?
When a bot is removed, related history entries are no longer available.
Why do some entries have no comment?
The comment is optional; if it was left empty at publish, the field stays blank.