Voice Agent
Reference

Troubleshooting and common errors

Resolve common result, upload, capacity, permission, and connection problems.

A metric has no score

Open Metric scoring first. Needs setup means required context is missing; Not scored means the available evidence could not support a score. A completed uploaded run with no score may still be waiting for metric computation.

The run page can say: “Recording and transcript can be reviewed while metrics finish computing.” Review those artifacts while you wait.

Processing is taking longer than expected

Refresh the suite or run and check its status. Processing duration depends on the recording, requested work, and current deployment load. Do not assume a fixed completion time.

The product says it is at capacity

A saturated deployment can return a recoverable capacity error. Wait and retry. If you need help, include the request reference shown in the error message when contacting support.

Common recoverable client messages include:

  • “Network error. Please check your connection and try again.”
  • “Request timed out. Please try again.”
  • “Service temporarily unavailable. Please try again in a moment.”

A generated call did not complete

Open the run and read the visible Failure reason before taking action.

What you seeCheck and recover
Queued or startingWait for capacity, then refresh the suite or run. Do not assume a fixed start time or submit duplicates while it is still progressing.
BusyCheck the selected number and call direction, wait for the destination line to become available, then retry only after the prior attempt is no longer active.
No answerConfirm the AUT number and direction, then retry only if the endpoint should have answered.
TimeoutCheck endpoint reachability and its call configuration; retry after correcting a transient endpoint or capacity problem.
CanceledConfirm whether someone stopped the run intentionally. Start a new run only when a new attempt is wanted.
Failed or no recordingUse the stated reason, verify the number, direction, endpoint reachability, and configuration. A missing recording can mean the call never connected, so do not retry blindly.

Run Test is disabled

Select a vertical, call scenario, and at least one main, robustness, or bias metric. Members must also select a registered AUT with a configured vertical. Resolve any applicable Policy Enforcement readiness message; it requires ready extracted policy rules for the selected AUT.

Policy Enforcement is not ready

On Agents, review the policy status and warnings. Use Extract policies for a stored definition that has not been extracted and Refresh policies when that control is shown. Existing definitions are read-only: for missing, empty, or incorrect rules, delete and recreate the registration with a corrected definition. Retry a failed extraction when the failure was transient. Then regenerate the scenario before running it.

I cannot access a workspace or administration page

Workspace access denied means your selected workspace is not in your memberships. Confirm the workspace first. Ask an administrator for organization tasks; Settings requires super-admin access.

An upload or channel looks wrong

Unsupported files are skipped with: “Unsupported files skipped. Upload WAV, MP3, M4A, or FLAC recordings.” For stereo audio, select L or R instead of Auto if automatic channel selection assigns the AUT incorrectly.

Delete did not clearly succeed or fail

Refresh and confirm whether the suite or run still exists before submitting another destructive request. This avoids repeating a deletion whose network result was unclear.

See supported files and current limits

On this page