Skip to main content

Test a run

1

Start the run

Save, then click Test. Start a test run shows one field per input variable. Fill callee_name and callee_number (your own number, for example +91 98765 4xxxx), then click Start run.
2

Watch it

The canvas switches to run view. A banner shows Running, then Completed, Failed or Cancelled. Blocks the run has finished show a green check; a failed block shows a red cross. Click Exit to return to the editor.
Workflow canvas in run view with the banner Run Completed and an Exit button; the Agent, Condition and Action blocks each show a green check

A completed test run

The banner shows Completed and every block on the path has a green check. The run also appears in Logs → Workflows.
A test run is not a simulation: it places real calls with the values you typed, charged like any other call. Each call follows its Agent block’s call window and retries, so a test started outside the window waits for it to open. A test run may call from a Ringg test number. An Await block in the path holds the run for its full wait.

Publish and versions

1

Click Publish

The editor checks the graph first. If anything blocks publishing, you see a message such as “3 issues block publishing”, the Issues panel opens and each affected block shows a red count.
2

Confirm

The dialog reads “Publishing makes the workflow available to run.” Click Publish.
Dialog titled Publish “Payment reminder follow-up”? reading Publishing makes the workflow available to run, with Cancel and Publish buttons

The publish confirmation

You see “Workflow published” and the status becomes Active.
Each publish creates a version. The version picker sits next to the name in the breadcrumb, listing each version with Active or Draft. To change a published workflow, edit it and click Save: your edits become a draft version and runs keep using the active one. Click Publish again to make the draft active. Older versions open read-only, with a bar saying “A newer version of this workflow exists”.