Inspect voice sequence runs
Open a sequence from Sequences, then select Runs. A run records an actual admitted call workflow. Simulation previews do not create runs.
Find the call workflow
- Check the list's mode, status, version, and time filters.
- Open the run and review its start time and Started by information.
- Check whether it used a saved draft or a published version.
- Follow the call references when you need the telephone outcome.
Incoming runs identify the receiving number. Manual runs identify the initiating user or API key where available. The retained definition belongs to that run; editing or publishing later does not replace it.
Understand status
| Status | Meaning |
|---|---|
| Queued | Accepted and awaiting execution. |
| Running | Executing the call workflow. |
| Waiting | Waiting during call activity. Inspect the current step for context. |
| Succeeded | Reached a successful workflow ending. |
| Failed | Ended with a technical failure or a configured failed result. |
| Canceled | Cancellation was confirmed. |
A successful workflow can include a handled busy or no-answer outcome. It does not establish that a particular recipient answered or that an external business action succeeded.
Inspect steps and results
Select a step occurrence to inspect its input, selected output, result, and timing. A transfer can revisit an entry or step; inspect the occurrence associated with the problem.
Use Finish with a result outcomes to distinguish business endings such as no_input from technical failures. A deliberate failed result may have a reason without a technical error code.
Private keypad observations and sensitive values may be absent from retained detail. An absent historical value cannot be reconstructed from today's draft. Recording and transcript state belongs to the recordings view.
Cancel a run
- Open an active run and select Cancel run.
- Review and confirm the request.
- Wait for the displayed status to reach a terminal state.
A pending cancellation is a request to stop, not confirmation that the call ended. Normal completion can win a race with cancellation, and unconfirmed cleanup can result in failure. Inspect the final status.
Cancellation cannot undo actions already completed. Pause the sequence separately when it should accept no new production calls.
Understand retained detail
Detailed snapshots, input, results, and step occurrences expire 30 days after the run ends. A thin summary can remain after detail expires. Deleted sequences become unavailable through ordinary history views before background cleanup finishes.
If detail is temporarily unavailable, retry later. If it is expired, aggregate metrics do not restore it. Call and recording records have their own retention and availability.
Next steps
Powiązane zasoby
Kontynuuj z dokumentacją, przewodnikami i przykładami dotyczącymi tego tematu. Zasoby są w języku angielskim.