Open the file in a plain text editor and check the delimiter and the first few rows. Save as UTF-8 CSV with commas, or tell the ingestion step which delimiter to expect. Add a row-count check to whatever produces the file, so empty exports are caught before upload.

Error Library / AEP

Batch ingestion failed or wrote 0 records: empty or header-only file

What you seeBatch completed with 0 records, or failed with no row errors

A file with only a header row, a different delimiter than expected, or an encoding problem can produce a batch with nothing in it.

Why it happens

The export ran before the data was ready and only wrote the header.
The file uses semicolons or tabs, so each line is read as one long column.
A byte-order mark or unusual encoding corrupts the first column name.

How to fix it

Open the file in a plain text editor and check the delimiter and the first few rows.
Save as UTF-8 CSV with commas, or tell the ingestion step which delimiter to expect.
Add a row-count check to whatever produces the file, so empty exports are caught before upload.

Before and after

Fails

event_id;event_timestamp;page_name  (semicolons, read as one column)

Works

event_id,event_timestamp,page_name

Common questions

Why no error message?

Nothing failed validation because nothing was read. Check the file, not the schema.

Practise the fix

Build the Customer Profile

Reproduce this error in your own AEP practice workspace, fix it, and earn a verifiable credential for the skills involved: XDM schema design, Identity descriptors, Real-Time Customer Profile enablement, Dataset configuration.

See the Lab plan

Related errors

Batch ingestion: columns missing from the dataset after upload

XDM ingestion error: "Missing required field" (_id, timestamp)

AdsBot is an independent training provider, not affiliated with Adobe. Behaviour can differ between ingestion methods and product versions; always test with a small batch first.