Skip to main content
Version: 0.9.17-patch1

Draft and publish

Every flow you edit in the Flow Designer is a draft. Drafts are safe to mutate at will and can be tested in isolation. Once you're happy with the result you publish it — that's when it becomes the version that real callers actually reach.

Who can save and publish​

Team roleSave draftPublish
VIEWERNoNo
MEMBERYesOnly when the team allows Members can publish Apps (team admin setting).
ADMIN / SUPERUSERYesYes

The server enforces these rules even if the UI is stale. Team admins toggle Members can publish Apps under Settings → Team.

The legacy "Sync app" button is gone. Publish replaces it.

Lifecycle at a glance​

Each flow has a version history with three statuses:

StatusWhat it means
DRAFTYour in-progress edits. Not served to real endpoints.
PUBLISHEDCurrently live. Conversations routed to this app's endpoints run against this definition.
ARCHIVEDA previously published version superseded by a later publish. Kept for audit and revert.

At any moment there is exactly one published version per flow (or zero, on a brand-new app). Saving in the editor always writes to the draft — it never silently mutates the published version.

Draft mode​

When you're editing, you're working on the draft. Two things happen behind the scenes:

  • Autosave — the draft is persisted to the platform as you edit, so you can close the tab and return.
  • Test endpoint — the first time you run a test call, the Flow Designer creates a temporary WebRTC endpoint that points at the draft. Subsequent tests reuse the same temporary endpoint and re-push the latest definition.

Running a test call​

Click Test in the toolbar. The browser opens a WebRTC session against the temporary endpoint and the draft definition runs end to end. The test panel below the canvas shows:

  • Connection status (preparing / connecting / running / ended).
  • Inline conversation events (user turn, agent turn, tool call, transition).
  • A link to the resulting conversation record after the call ends.

A single voice-agent node can also be tested in isolation — the Flow Designer wraps it in a minimal "single voice node" flow on the same temporary endpoint, useful for prompt iteration.

What test calls do not do​

  • They do not invoke real PSTN — even if the flow has a phone endpoint, the test uses WebRTC.
  • They do not mutate the published version.
  • They do not touch the real endpoint's traffic.

Publishing​

When the draft is ready, click Publish in the toolbar.

  1. The current draft becomes a new PUBLISHED version (with an incremented version number).
  2. The previous published version is moved to ARCHIVED.
  3. The real endpoint(s) on the platform are re-synced to point at the new version. This is immediate — the next call arrives at the new flow.

If there is no draft (you're looking at a flow that hasn't been changed since the last publish), the Publish button is disabled and the toolbar shows "Already live — make a change to publish a new version".

Reverting​

From the Version History drawer you can:

  • Load any previous version into the editor as a new draft (useful for inspecting or copy-editing).
  • Revert the current draft back to a previous version's content. The revert itself is a draft action — you still need to publish for the change to go live.
  • Rollback to a published version when you need to restore a known-good live flow. The selected historical version becomes the new draft, so you can inspect it, run a test call, and publish it deliberately.
  • Delete an unwanted draft when you want to discard the in-progress draft and return to the published version.
Rollback is still controlled

Restoring an older published version does not silently change live traffic. It creates a draft from the historical version; publish it only after you have reviewed or tested it.

Editing a live flow​

Because publishing is a single click, the safest pattern is:

  1. Open the flow. The canvas shows the currently published version (as a draft).
  2. Make your changes.
  3. Run one or more test calls.
  4. Publish.

If you want to keep iterating without going live, just don't publish — the draft will stay around indefinitely and the previously published version keeps serving real traffic.

See also​