DialNexa Batch Call Retries And Statuses

Understand DialNexa batch call statuses, campaign lifecycle, recipient call statuses, retry count, retry interval, retry expiry, and result counters.

DialNexa batch call statuses show whether a campaign is being drafted, waiting to run, actively sending calls, paused, completed, or cancelled. Recipient results inside that campaign still use call statuses such as completed, did_not_pick, busy, no_answer, failed, cancelled, and retry_expired.

Read campaign status and recipient call status separately. A campaign can be running while many recipient calls are still created, initiated, or sent.

Batch Call Statuses

These statuses apply to the campaign container.

Status	Final?	What it means	What to do next
draft	No	The campaign is saved for review and is not placing calls.	Review recipients, dynamic variables, number, schedule, and retries.
active	No	The campaign is ready or scheduled, but calls are not currently being processed. It may be waiting for its start time or for another running batch to finish.	Confirm start time and readiness. Pause or cancel if it should not run.
running	No	DialNexa is preparing, sending, or monitoring calls for the campaign.	Watch Call History, sent count, picked-up count, and retry history.
paused	No	New call processing is stopped temporarily. Calls already initiated can still finish.	Resume when ready or cancel if the campaign should stop permanently.
completed	Yes	All recipients reached final counted outcomes.	Export results and separate completed, failed, and did-not-pick groups.
cancelled	Yes	The campaign was stopped permanently. Queued calls are removed and queued call logs can be marked cancelled.	Create a new campaign if you need to call the list again.
initiated	API acknowledgement	The legacy /batch-calls create response was accepted and returned a batch id. It is not the long-running campaign state.	Fetch the campaign or campaign-linked call logs for current status.

Recipient Call Statuses

Each recipient attempt becomes a call log. These statuses are the ones you filter and export from Call History.

Call status	Final?	Meaning in a batch campaign	Common follow-up
created	No	The recipient call log exists and is queued or prepared.	Wait for progress. Investigate if it stays here too long.
initiated	No	Call setup has started.	Wait for provider updates.
sent	No	The outbound request was sent to the provider.	Monitor for connection or final outcome.
received	No	DialNexa received an inbound or provider callback event.	Wait for a later call event.
completed	Yes	The call connected and ended.	Review transcript, summary, fields, and end_reason.
did_not_pick	Yes	The recipient did not answer or voicemail was detected.	Retry if rules allow, or export for follow-up.
busy	Yes	The line was busy or rejected as busy.	Retry later or export with no-answer outcomes.
no_answer	Yes	The provider returned no answer.	Review route and retry strategy.
failed	Yes	The call failed before a useful conversation.	Inspect end_reason, number validity, route, wallet, and provider errors.
cancelled	Yes	The call was stopped before completion, often because the campaign was cancelled.	Confirm the cancellation was intentional.
retry_expired	Yes	Retry handling ended without a successful final result.	Review retry count, retry interval, and attempt history.

Retry Controls

Retry settings are configured before launch.

Control	Behavior
Retry count	Number of additional attempts after the first attempt. The create page validates this value before sending.
Retry interval	Time between retry attempts. The create page validates that a non-zero retry count has a non-zero interval.
Zero retries	Each recipient receives only the first attempt.
Retry history	Call History can expand a call row to show retry attempts.
Retry expiry	A recipient can end as retry_expired when retry handling no longer has an eligible attempt.

Campaign Counters

Use counters to understand campaign progress, but use Call History for exact recipient evidence.

Counter	What it means
Recipients	Total recipients loaded into the campaign.
Sent	Recipients for whom a call attempt was sent.
Picked Up	Calls that connected.
Completed leads	Calls counted as completed.
Failed leads	Calls counted as failed, including failed, busy, and no-answer outcomes.
Did not pick count	Calls counted as did not pick.

How Statuses Affect Exports

1. Filter by campaign

   Open Call History through the batch campaign or use the batch call id filter.

2. Separate final statuses

   Export completed, failed, cancelled, did-not-pick, busy, no-answer, and retry-expired groups separately when operations needs different follow-up.

3. Keep in-progress rows out of final reporting

   created, initiated, sent, and received are not final outcomes.

4. Review end reasons

   Use end_reason to separate invalid numbers, busy lines, destination blocks, voicemail, capacity, and balance problems.

Tune Retries For A Campaign

1. Start with a small run

   Estimate answer rate, busy rate, and invalid-number rate before scaling.

2. Use a realistic interval

   Avoid retrying so quickly that recipients experience duplicate calls.

3. Check final status distribution

   Compare completed, did not pick, busy, no answer, failed, cancelled, and retry expired rows.

4. Clean the next list

   Remove invalid numbers, update preferred timing, and adjust the message before the next campaign.

Troubleshooting Batch Statuses

Campaign is active but no calls are going out

Check start time, workspace readiness, outbound number assignment, wallet balance, and whether another campaign is already running for the organization.

Campaign is running but recipient rows are still created

Give the scheduler and provider updates time to progress. If rows stay stale, inspect route readiness and queue processing.

Campaign was cancelled but some calls completed

Calls already initiated before cancellation can still finish. Cancellation stops queued and future work.

Retry count looks higher than expected

Count the first attempt plus additional retries. Retry count controls extra attempts, not total attempts.

Related Reading

Recipient Results

Read recipient outcomes and export rows.

Call History

Filter and inspect campaign-linked calls.

Retry Review

Inspect retry chains.

Statuses Reference

Compare call, batch, workflow, and transfer statuses.