Invalid CSV File Ingested into Amazon S3

Issue

The ingestion process into Amazon S3 fails.

Possible Cause

The uploaded CSV file does not meet the required formatting standards. This makes the file unreadable or incompatible for Data Cloud processing. Some of the common formatting errors could be:

• Missing header row

• Mismatched number of columns in data rows vs. header

• Unsupported delimiters such as semicolon (;) and pipe (|).

• Extra blank lines or irregular row counts

• Incorrect encoding (must be UTF-8 without BOM)

• Unexpected characters (non-ASCII or non-standard symbols)

Advanced Troubleshooting Steps

Use the following CSV checklist to prepare your file:

1. The first row contains column headers.

2. Each data row matches the header column count.

3. Comma (,) is used as the delimiter.

4. The file is encoded in UTF-8 without BOM (ensure no extra characters at the start of the file).

5. No extra blank lines at the end of the file.

6. Values are cleaned and type-matched (For example, no text in number-only columns).

After you validate and correct your file:

1. Save it in the correct format.

2. Upload the updated file to S3.

3. Restart the ingestion process.