## TL;DR
A bulk list stuck at 0 percent usually means the upload did not parse: wrong file format, bad encoding, or a header row the parser choked on. Re-upload a small clean CSV (UTF-8, one email per row, no header surprises) and watch it move. If a clean small file also sticks, the job queue is backed up and you wait or contact support.

```text
millionverifier bulk list stuck at 0 percent processing
```

## Use this when
- The bulk dashboard shows 0 percent for an hour or more.
- Smaller lists process fine.
- The file came from an export, not hand-built.

## Not for this skill when
- The list errors out. That is a parse failure with a message, a different fix.
- Single verifications fail. That is account or credit trouble.

## Steps
1. Check the file: UTF-8 encoding, comma-separated, one email per row, no merged cells or multi-sheet workbooks. Verify: opening it in a text editor shows clean rows.
2. Upload a 10-row test file from the same source. Verify: the test processes, proving the pipeline works.
3. If the test works, bisect the real file: split it and upload halves. Verify: you find the chunk with the bad row.
4. Look for the usual poison rows: blank lines, header text mid-file, quoted commas, non-email junk. Verify: removing them unsticks the list.
5. If even the clean 10-row file sticks at 0 percent, check the status page and contact support with the job ID. Verify: the stall is platform-side.

## Variant phrasings
### millionverifier bulk not processing
The short search, same file-format diagnosis.
### bulk verification stuck 0%
Percent phrasing, points at step 1.
### millionverifier upload frozen
Upload phrasing, lands on the bisect.

Compatibility: MillionVerifier bulk verification. The parser is picky about encoding and structure.

## Why it happens
Bulk jobs parse the whole file before processing starts, and one malformed row can hold the parse at zero with no useful error. Exports from CRMs and spreadsheets are full of encoding quirks, smart quotes, and stray blank rows that look fine in Excel and break a CSV parser. The 0 percent is the parser refusing to start, not slowness.

## Edge cases / pitfalls
- Excel "CSV" exports are often not UTF-8. Re-save explicitly as UTF-8.
- A header row is fine if the tool expects one; a header row mid-file is poison. Know which.
- Do not re-upload the same broken file repeatedly hoping it clears. Fix the file.
- Very large lists can legitimately sit at 0 percent for a while during queue backup. Give it an hour before declaring it stuck.

## Provenance

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