JOB_INPUT_EXPIRED
The list the bulk job ran on is no longer stored
A resume was asked for a run whose uploaded list has passed out of the retention window, so there is nothing left to re-run.
- http status
- 409
- credits
- Nothing is billed for a failed request.
What it means
A run keeps the list it was given for the retention window published on the endpoint's reference page, and the job's row and its files are removed together at the end of it. Resuming replays that stored list from the top, so once it is gone the run cannot be resumed whatever its status says.
Nothing is queued and nothing is charged.
What to do
Create a new job with the rows you still need. To keep a long-running list resumable, download its results and re-create it inside the retention window.
Example response
{
"success": false,
"error": {
"code": "JOB_INPUT_EXPIRED",
"message": "The list this run was created from is no longer stored, so the run cannot be resumed. Create a new job with the rows you still need.",
"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_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_INPUT_EXPIRED.md