JOB_FAILED
The bulk job failed before producing results
Results were requested for a job that failed before a single row was written, so there is no results file.
- http status
- 409
- credits
- Nothing is billed for a failed request.
What it means
A run that fails part-way keeps the rows it did write and serves them normally: those rows were billed, so withholding them would charge for work you could never collect. Only a job that failed with zero processed rows answers with this code, and nothing was billed for it.
What to do
Create a new job with the same rows. If it fails again, quote the request id when you get in touch.
Example response
{
"success": false,
"error": {
"code": "JOB_FAILED",
"message": "The job failed before any addresses were processed, so there are no results. Nothing was billed.",
"request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
}
}Every error carries the request_id also sent in the X-Request-Id header; quote it when writing to support.
Related
- RESULTS_NOT_READY · the bulk job has not finished yet
- JOB_ALREADY_FINISHED · the bulk job cannot be cancelled any more
- JOB_CANCELLED · the bulk job was cancelled before producing results
- JOB_NOT_RESUMABLE · the bulk job is not in a state a resume can recover
- JOB_INPUT_EXPIRED · the list the bulk job ran on is no longer stored
- JOB_NOT_FINISHED · the bulk run has not finished, so there is no completion webhook to send
- WEBHOOK_NOT_CONFIGURED · the bulk run has no webhook URL to deliver to
- IDEMPOTENCY_KEY_REUSED · the Idempotency-Key was already used for a different bulk request
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/JOB_FAILED.md