Skip to content

Running a test

There are three places to start a test run.

From a scenario

Useful when you want to run all paths at once:

  1. Open the scenario.
  2. Click Run all paths.
  3. The platform queues every path on the scenario. Runs execute with bounded parallelism and you can leave the page; runs continue server-side.

You’ll see each path’s status update independently in the path list.

From a single path

Useful when you’re iterating on one specific narrative:

  1. Open the scenario, click into the path you want.
  2. Click Run.
  3. The live transcript streams in if you stay on the page; otherwise watch from the Test results feed.

From the queue page

The Queue page in the left nav shows everything that’s running, queued, or recently finished across the workspace. You can pause, retry, or cancel from here.

What happens during a run

StageWhat you see
QueuedStatus pending. Picked up within seconds normally.
MaterializingStatus flips to running. Caller persona is composed from the scenario + path.
Live conversationVoice: a real call is placed. Chat: a session opens. Transcript streams in turn-by-turn.
FinalizingConversation ended. Transcript closed, audio finalized, success criteria evaluated.
DoneStatus completed. Click in to view the result.

A small fraction of runs end in failed instead of completed — that means a platform-level error stopped the run before a real conversation happened (target unreachable, network error, etc.). A failed run is different from a passing-but-bad-result; failed = we couldn’t even test.

Watching a live call

The live view shows:

  • Transcript appearing turn-by-turn as it’s recognized.
  • Tool invocations highlighted as they fire (end_call, press_digit, your custom functions).
  • Live latency for the most recent turn.

You don’t need to keep this open. The run completes whether you watch or not.

Outbound vs inbound differences

  • Outbound — AssureAgent dials the target’s number from one of your provisioned outbound numbers. Caller speaks first.
  • Inbound — the run is “armed” and waits for the target to dial in. The status sits at running from the moment you click Run; the actual call begins when your IVR / system places it. If the inbound call doesn’t arrive within the configured window, the run times out.

Cancelling

Click the Cancel action on a running or pending run. Live calls are hung up; queued runs are removed from the queue. A cancelled run shows up in the report list with status cancelled.

Why a run might fail

FailureWhat to check
target_unreachableTarget phone number wrong, or the target system isn’t accepting calls.
caller_voice_unavailableThe voice configured on the agent is temporarily unavailable upstream. Pick a different voice.
tool_sync_pendingCustom functions haven’t synced yet. Check the Functions panel banner; click Retry if it’s red.
duration_cap_no_progressThe conversation hit the max duration without natural end. Either raise the cap on the agent, or add tighter end conditions to the scenario description.
errorPlatform error. Surfaced in the run detail; safe to retry.