---
title: "How to view scenario version history in Scenario Builder"
description: "Use the Version history window, comments, previewing a snapshot, and publishing it as the current scenario."
---

# 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

- [x] You are logged in with integrator or administrator rights.
- [x] Scenario Builder is open for the target bot.
- [x] If the version list is empty or the feature seems unavailable, contact your instance administrator (history storage may be restricted).

---

## How to open version history

1. Open the bot in **Scenario Builder**.
2. On the toolbar, click the **history** icon (tooltip: **Version history**).
3. 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

1. Click a row — it becomes selected.
2. The right-hand panel shows a comparison (current vs selected).
3. Click **Preview** — the editor opens that version’s graph (the URL includes a version preview parameter).
4. 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

1. Click **Publish** on the toolbar.
2. In the **Publish Scenario** dialog, fill in **Version comment**.
3. Confirm publish.

### After save

1. Open **Version history**.
2. Find the entry and use the comment (pencil) control to edit the description.
3. 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.

1. In **Version history**, select an entry and click **Preview** to verify it is the right state.
2. On the toolbar, click **Publish** (while viewing a history snapshot, the UI indicates you are in history preview mode).
3. 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.
4. 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.

---

## Related articles

- [Edit scenario](/en/scenariobuilder/how-to/edit-scenario.md)
- [Scenario Builder hub](/en/scenariobuilder/integrator-hub.md)
- [Scenario versioning: why it exists and how it works](/en/scenariobuilder/reference/version-history-explained.md)