How to test a scenario in Scenario Builder?

Scenario Builder is a new module that replaces Scenario Dialog. This guide helps you run a scenario to verify it works, view run history, and use the chat preview.

When you need it

  • You need to verify the scenario works correctly after changes.
  • You want to see how the dialog looks for the bot user.
  • You need to find an error in the logic or node configuration.

What you need to know

  • Full run — the scenario runs from the beginning (Start Node). During execution you can interact via the chat preview.
  • Run history (Runs) — the left panel stores history of all runs. For each run you can see executed nodes and status.
  • Chat preview — a widget that shows the dialog in real time during the test. You can send messages and see bot responses.
  • Test single action — for Action nodes you can test the action without running the full scenario (see Use action in scenario).

Before you start

  • You are logged in with integrator or administrator rights.
  • You have an open scenario in Scenario Builder.
  • The scenario is saved (no critical validation errors).

Step-by-step instructions

1. Run the scenario

  1. In the top toolbar, click «Run» or «Test».
  2. The system validates the scenario. If there are errors — the run is blocked and an error list is shown.
  3. After successful validation, a new run is created. The execution indicator is displayed (running, success, error).

2. Interact via chat preview

  1. During execution, open the chat preview (if it does not open automatically).
  2. The chat widget shows bot messages and lets you send a response (text, buttons).
  3. Send a message — the scenario continues execution according to its logic.

3. View run history

  1. In the left panel, find the «Runs» section.
  2. Select a run from the list — information about executed nodes and status is displayed.
  3. You can view execution logs if the run ended with an error.

4. Stop execution (optional)

  1. During execution, click «Stop» in the toolbar.
  2. Execution is interrupted; the state is saved in run history.

5. Save changes after testing

  1. If you found changes needed during the test — make them in the scenario.
  2. Click «Save» or Ctrl+S (Mac: Cmd+S).
  3. Run the test again to verify.