agent silently truncated the csv import at 50000 rows

TL;DR

The importer silently stopped at 50,000 rows. Check for row limits in the importer, chunk the file, and verify row counts.

Error

csv import truncated at 50000 rows

Steps

1. Count source vs imported rows Expected: you confirm the truncation.
2. Check the importer for row limits Expected: you find the cap.
3. Chunk the file and import each chunk Expected: all rows land.
4. Assert row counts after every import Expected: it cannot regress.

When to use

• Import truncated at 50k rows
• A row limit cut it off

When not to use

• Counts match (then rows failed validation)
• The file has 50k rows (then nothing is wrong)

Tool compatibility

• CSV imports
• Row limits

Variant phrasings

import truncated 50000

Chunk the file and verify row counts.

csv stopped at 50k rows

Same: a row limit cut it off.

Why it happens

Limits hide in library defaults. Agents never check because small test files pass.

Edge cases

• Some limits are per-batch; chunk accordingly
• Log the truncation instead of staying silent

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nTjn8zhKFfPuKW4Ohvkw4Q