Skip to main content
Every Config Workflow supports version management — allowing you to evolve your routing logic safely without disrupting live traffic.

​
Version States

StatusDescription
DraftWork-in-progress. Not handling live traffic. Edit freely.
Published (Active)The currently deployed version. All live requests use this version.
InactiveA previously published version. Kept for reference and rollback.

​
Version Lifecycle

1

Create Draft

Every new Config starts as a draft version (e.g., v0.0.1). Build your flow, add nodes, and configure routing.
2

Publish

When ready, click Published (dropdown in the top right) and select Publish. This makes the version active and starts handling live traffic.
3

Iterate

Create a new draft version to make changes. The published version continues serving traffic while you iterate.
4

Promote or Rollback

Publish the new draft to promote it, or reactivate a previous version to rollback.

​
Export

Published versions can be exported as configuration files using the Export button in the top toolbar. This is useful for backup, migration, or infrastructure-as-code workflows.
Always create a new draft version before making changes. This ensures your live traffic is unaffected while you iterate.