Skip to main content
Common DialNexa batch call upload errors usually come from file format, recipient phone number values, dynamic variable mapping, file size, or selected outbound route. Fix the mapped preview before saving or starting a campaign.
If the preview table looks wrong, the campaign will not become wiser after launch.

​
Upload Error Checklist

Use this table before retrying an upload. DialNexa Match CSV Columns modal with mapped phone number, defaulted variables, and an unmapped fields warning.
ProblemWhat to fix
No phone number columnAdd a clear phone number column or choose the correct column in Match CSV Columns.
Unsupported file typeUpload a CSV or supported spreadsheet file.
File too largeFiles are limited to 10 MB. Reduce the file size or split the campaign.
Variable header mismatchUse Match CSV Columns to map your headers to the selected agent version variables.
Empty required valuesFill required recipient numbers and important variables.
Duplicate phone numbersLeave Skip duplicate phone numbers on for one call per number, or remove the file and turn it off before upload when repeated calls are intentional.
No selected outbound numberSelect a number with an outbound agent version before downloading or uploading the template.
Unsupported country or prefixEnable the destination route in Workspace Settings > Telephony Config, or change the recipient number.
Many row-level validation failuresDownload the errors CSV, fix the listed rows, and upload the corrected recipient file.

​
Destination Validation Errors

Recipient numbers are checked against the same route rules used by single outbound calls.
Error typeWhat to fix
Invalid phone numberAdd the country code, remove extra characters, or correct the digit count.
Unsupported destination countryEnable the destination country in Workspace Settings > Telephony Config, or use a route that supports it.
Unsupported prefixCheck whether the number matches the most specific enabled network group prefix for that destination country.
No enabled countries configuredEnable at least one network group for the selected provider before uploading the file.
When more than three rows fail, the upload page shows Download errors CSV with a position, phone_number, and failed_parsing_reason per failed row. DialNexa Create Batch Call page showing the Download errors CSV button after multiple recipient validation failures. The error CSV button is single-use. After downloading the report, fix the original CSV and upload it again.

​
Clean A Failed Upload

1

Download the template again

Use the template for the currently selected number and agent version.
2

Copy data into the template

Keep headers unchanged while moving rows over, or map your existing headers in the upload modal.
3

Remove formatting clutter

Avoid merged cells, hidden formulas, and non-CSV spreadsheet features.
4

Upload a small sample first

Test the first few rows before uploading the full list.
5

Check the preview

Confirm phone numbers and variables appear in the expected columns.

​
File Problems That Look Like Product Bugs

The agent expects the exact variable key after mapping. Use the modal to map readable headers to agent variable keys.
Check whether your file already includes country code before entering local digits.
The dashboard groups destination validation failures by message and row number. When more than three rows fail, use Download errors CSV to get position, phone_number, and failed_parsing_reason for each failed row.
The create page skips duplicate phone numbers by default and keeps the first row for each non-empty number. Remove the uploaded file and turn off Skip duplicate phone numbers before uploading again if repeated calls are intentional.
CSV values with commas need proper quoting. Use a spreadsheet export instead of hand-editing when possible.
Template variables depend on the selected published agent version.

Recipient Files

Prepare a clean CSV.

Dynamic Variables

Match headers to placeholders.

Recipient Results

Review uploaded rows and outcomes.