status is nonterminal. A terminal resource remains retrievable and does not transition back to active work.
Call status
The diagram shows allowed API-visible transitions, not one required path. A late callback, worker update, or reconciliation pass can skip intermediate observable states and advance
queued or dialing directly to in_progress or completed. Clients must accept any depicted transition. Cancellation is supported from queued, dialing, or in_progress.
Batch status
The controls match the diagram: start moves
draft to scheduled or queued; pause accepts scheduled, queued, or in_progress; resume moves paused back to scheduled or queued according to schedule eligibility; and cancel accepts every nonterminal batch state.
These transitions are not one required path. A late callback, worker update, or reconciliation pass can skip intermediate observable states and advance scheduled or queued directly to in_progress, completed, or failed along a depicted edge. Clients must accept every depicted transition and stop polling only at a terminal state.
Automation run status
answer_status is independent
answer_status belongs to a call and is not a lifecycle state. It may be answered, no_answer, busy, voicemail, or unknown.
Always decide whether to stop polling from
status, then interpret destination behavior from answer_status.