# csv import failed truncated at 500 rows questionnaire: how to fix it

A questionnaire CSV import that truncates at 500 rows has hit a row limit in the importer or a timeout disguised as success. Split the file into chunks under the limit and import them in sequence. Verify the total row count after each chunk so nothing goes missing silently.

```text
csv import failed truncated at 500 rows questionnaire
```

## When to use this skill
- Imports stop at a round row count
- The import reports success but questions are missing

## When not to use this skill
- The import errors outright (a structural issue)
- Rows are missing randomly, not at a clean cutoff (a data issue)

## Tool compatibility
RFP questionnaire CSV imports with row limits.
Related area: CSV and Excel data import pipelines.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with imports stop at a round row count, start at step 1 below.
- If instead the import errors outright (a structural issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Confirm the truncation

```
Count the imported questions and compare against the source file row count.
```
Expected: imports stop at a round number like 500.

### 2. Split the CSV into chunks

```
Divide the file into parts under the limit, keeping the header row on each.
```
Expected: multiple smaller files ready to import.

### 3. Import chunks in order

```
Upload each chunk sequentially, waiting for each to finish.
```
Expected: every chunk imports fully.

### 4. Verify the total

```
Count all imported questions against the source total.
```
Expected: the counts match exactly.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (confirm the truncation): Expected: imports stop at a round number like 500.
- Step 2 (split the csv into chunks): Expected: multiple smaller files ready to import.
- Step 3 (import chunks in order): Expected: every chunk imports fully.
- Step 4 (verify the total): Expected: the counts match exactly.

## Quick recap
1. Confirm the truncation
2. Split the CSV into chunks
3. Import chunks in order
4. Verify the total

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### csv import truncated 500 rows
Chunk under the limit and verify totals. If this matches what you saw, the steps above apply as written.

### questionnaire import missing rows
Silent truncation is worse than an error, always count. If this matches what you saw, the steps above apply as written.

## Why it happens
Importers often cap rows per job for performance, and some report success after silently stopping at the cap. Without a row count check, the missing questions go unnoticed until the RFP is half answered.

## Edge cases
- Keep the header row on every chunk
- Import order can matter for numbered questions
- Ask support for the documented limit so you chunk correctly

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6zI-NSgnKejNR9aMVzD1iw