Skip to main content

​
Test a working copy

  1. Resolve the issues shown below the canvas. Click an issue to locate the relevant step or setting.
  2. Click Test, fill in Workflow inputs, and choose Start test conversation.
  3. Talk through the flow, then use End conversation when finished.
Tests make real calls and use configured tools. Use test records and review the selected connections before testing actions that change external data.
Each test uses a saved working copy. Edits made during a test apply to the next test. Published dependencies, including subflows, stay pinned to their selected versions. Use Center beside the canvas zoom controls to bring the workflow back into view.

​
Inspect the result

Review the run status, conversation transcript, and per-step Inputs, Output, Transcript, and Evidence. The canvas highlights progress; task details show their completion or failure. External actions shows action results when present. A transcript may still be saving after a conversation ends. A missing final transcript should not be interpreted as a successful or empty conversation. Before publishing, exercise the normal path, each classification or branch destination, declined confirmations, authentication denial, and relevant error or timeout routes.

​
Publish a version

Click Publish version. Review the voice, optional face, task model choices, and subflow versions, then choose Compile and publish. Publication validates the workflow and creates an immutable revision. Keep the workflow revision UUID for your integration. A workflow’s name, working-copy ID, and version number are different identifiers. Use the revision UUID with Start a workflow run.

​
Changes and recovery

Edit the working copy, test, and publish a new version to release changes. Update your application’s selected revision only when ready. To return to an earlier behavior, select the earlier published revision. The Workflows page shows the latest published version and a newer working copy when one exists. Open History in the workflow editor to inspect the full saved-edit and publication history. Select an entry to compare snapshots or use Restore to draft, then test and publish the restored working copy. Historical revisions remain inspectable after a selected model is deprecated, but those revisions cannot launch new conversations. Choose an available model in the working copy and publish a new version. If another edit conflicts with yours, use Save separate copy to preserve your changes or Reload server copy to load the saved version. A recovery notice also offers Save recovered copy. Check the save status before leaving the editor.