409
Conflict
batch_not_retryable — Batch has no retryable rows
Message
What causes it
- The batch is not `completed` or `interrupted`, or it has no `failed` rows under the retry limit (3 attempts per row) and no `skipped` rows.
How to fix it
- Inspect `GET /batches/{id}/executions?filter[status]=failed` — rows that exhausted their retries stay failed and should be resubmitted in a new batch.
- Wait for a running batch to finish before retrying.
Operations that return it
-
POST
/batches/{id}/retry_failedRetry failed and skipped rows
Example response
HTTP/1.1 409 Conflict
· Content-Type: application/json
409 Conflict
{
"error": {
"code": "batch_not_retryable",
"message": "Batch is in status <status> and has no retryable rows.",
"details": [],
"request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
"doc_url": "https://cascades.crscreditapi.com/docs/api/errors/batch_not_retryable"
}
}