Publishing a scenario and version history

While building, you constantly change the scenario on the canvas. To make it run autonomously on a schedule or in response to events, you need to deploy the working version to production. This page explains how Dev and Prod work, how to deploy, and how to roll back to a previously saved version.

---

Dev and Prod: two states of a scenario

Every scenario always has two versions: Dev and Prod. Both versions exist in parallel and are fully independent of each other.

Dev (development environment)
This is where you build the scenario, test logic, and make changes. All runs here are manual and exist for testing and debugging.

Prod (autonomous version)
This is the autonomously running version of the scenario. It runs continuously: fires on a schedule, receives events from external sources, and executes tasks without manual input.

Deploying a scenario (Deploy)

Deploying copies the current Dev version into Prod.

First, look at the diagram to understand the transition logic:

1. Click Deploy in the scenario editor.
2. The current Dev version becomes the new Prod version.

Active toggle

After deploying, check the active status of the scenario.

• Active: the scenario runs autonomously, accepts events, and fires on schedule.
• Inactive: the scenario is deployed but automatic runs are paused.

Version history and rolling back

A new version is created every time you save or run the scenario. This lets you return to a previous working state, compare current logic with past decisions, and continue from a known good point. Switch between versions in the history panel to do this.

How to view and restore a previous version:

1. Open the version list.
2. Select a stable previous version.
3. That version immediately becomes your current version on the Dev canvas.
4. Review it and make any adjustments if needed.
5. Click Deploy to publish that version to Prod.

What's next

→ Testing and debugging scenarios

→ Execution history

→ Version history