How bulk jobs run, from upload to settle

The life of a bulk list: counting, the credit hold, running, pausing, the retry tail, and the refund when it settles.

A bulk job moves through a fixed lifecycle, and nothing is charged until you confirm it: upload → count → confirm → run → settle.

Upload and confirm

Paste addresses or upload CSV, Excel or JSON. Duplicates and non-email values are dropped before anything is counted. You then see the exact row count and worst-case cost, and credits are held, not spent, when you confirm.

While it runs

Jobs run through a fair queue; you can pause, resume or stop an active job at any time. Stopping refunds the credits for every row that never ran. Hit Refresh on the job page for the latest counts.

Why a job says "finalizing"

Near the end, the addresses left are the ones on slow or cautious mail servers (greylisting): they get a second pass before their verdicts settle. The job finishes on its own; nothing is stuck.

Settle, refunds and unknowns

When the job completes, the hold is settled: you are charged only for rows that reached a real verdict. Rows that finished unknown are not charged, and a completed job offers "Re-verify unknowns" to run just those again.

Still stuck? Open a support ticket and we'll reply in your dashboard.