delivery_not_retryable — Delivery not retryable

What causes it

• The delivery already `succeeded`, or a worker currently holds a claim on it (an automatic retry is in flight).

How to fix it

1. Only `failed` and `exhausted` deliveries need a manual retry; check `status` and `next_retry_at` first.
2. If the endpoint was down, fix it and retry once — each manual retry restarts the attempt counter's schedule, it does not add attempts.

Operations that return it

• POST /webhook_deliveries/{id}/retry Manually retry a failed or dead delivery

Example response

HTTP/1.1 409 Conflict · Content-Type: application/json

{
  "error": {
    "code": "delivery_not_retryable",
    "message": "Delivery is in status <status> and cannot be retried.",
    "details": [],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/delivery_not_retryable"
  }
}

Related

• Concepts › Webhooks