My export is stuck on Incomplete
Incomplete is a normal, resumable status rather than an error. Press Resume, and here is what to do if it keeps stopping.
An export showing incomplete has written some rows and stopped
early. It is not a failure, nothing is lost, and it is designed to be picked back
up.
Do this first
- Go to Account → Exports.
- Find the export and press Resume.
- It re-queues and continues from where it stopped.
You are billed only for rows the resume newly writes. Rows from the first attempt are not billed twice — how credits work.
You can download the partial file meanwhile
The rows already written are already yours. If you need to start working while the rest catches up, download it, then download again after the resume finishes.
Why a job goes incomplete
- Size. Very large jobs — hundreds of thousands of rows — are checkpointed deliberately. Stopping and resuming is cheaper and safer than holding one job open for an hour.
- A worker was recycled mid-job, during a deploy or a restart. The checkpoint is exactly what makes that harmless.
- A transient read error on part of the row set.
None of these should require anything from you beyond pressing Resume.
If Resume does not finish it
Resume more than once — it is safe, and a second pass clears most cases. If it stops at the same point twice:
- Note the export id (on the export's row) and the
done / totalfigures. - Email
support@findandclose.comwith both. That pair is enough for us to find the job. - If you need the data now, re-run the search with a tighter filter or a smaller area and export that. Rows you already exported in the last 30 days are not billed again, so splitting one big export into three smaller ones costs the same.
Incomplete versus Failed
| Status | Rows written | Credits | Action |
|---|---|---|---|
incomplete | Some | Billed for what was written | Resume |
failed | None usable | Reservation released in full | Try again, then contact us |
What "stuck" usually turns out to be
A queued job on a busy minute. queued is not
incomplete; it just has not started. Give it a minute before assuming anything is
wrong.
A big job that is working fine. Check the done / total
progress. If done is climbing, it is running, and you can close the tab —
exports run on our servers.
Over the API
POST /api/v1/exports/:id/resume re-queues the job and bills nothing new. See
exports over the API.
Updated on: