JOB_NOT_FINISHED
The bulk run has not finished, so there is no completion webhook to send
A redelivery of the completion webhook was asked for a run that is still queued or running.
- http status
- 409
- credits
- Nothing is billed for a failed request.
What it means
The completion webhook announces a finished run, so it exists only once the run has settled at completed, failed or cancelled. Until then there is nothing to send again — and sending the run's counts mid-flight would announce a finish that has not happened.
Nothing is delivered and nothing is charged.
What to do
Poll the run (`GET /api/v1/email/bulk/{jobId}` and its phone, IP, address and consistency twins) until `status` is terminal, then ask for the redelivery. If the run is still going, the first delivery has not been missed yet: it has not been made.
Example response
{
"success": false,
"error": {
"code": "JOB_NOT_FINISHED",
"message": "The run has not finished yet, so there is no completion webhook to send again.",
"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_FAILED · the bulk job failed 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
- 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_NOT_FINISHED.md