Restart Queued Batch Requests

“My asynchronous batch job appears stuck and some requests are still queued.”

Use this endpoint to re-submit queued requests for an existing batch job using its job ID.

When to use:

• A previously submitted asynchronous batch appears stalled (for example, pending for too long with no completion progress).
• You want to recover queued requests without creating a new job.

When not to use:

• The job is already complete.
• You need to submit a new search batch (use POST /v1/search).

Completed request and billing behavior:

• Already completed searches in the batch are not restarted.
• If the entire job is already complete, this endpoint returns 409 Conflict and no restart occurs.
• This is a recovery action for the existing job (no new job ID), and is not intended to generate additional billing for already completed work.

This operation re-queues queued requests under the same job so you can continue polling GET /v1/search/{jobid} for completion. The API key used must belong to the same organization as the job.