Retry a failed CV DeepMatch run

POST 
/api/v1/cvdeepmatch/:id/retry

Manually re-run a run that ended failed due to a transient pipeline error (errorCode: PROCESSING_FAILED). The retry re-runs the matching pipeline on the original CV inputs already stored — you do not re-upload anything.

A run is retryable only when all of the following hold (otherwise the request is rejected with no charge and no state change):

• status === "failed" and errorCode === "PROCESSING_FAILED" (an invalid-CV CV_NOT_RECOGNIZED run is never retryable);
• fewer than 2 retries used so far (3 attempts total);
• within 24 hours of the original submit;
• not already in progress;
• the original inputs are still available.

Each retry is a fresh charge (the failed attempt was refunded): the run reserves its cost again and settles normally — captured on success, refunded on failure. Poll GET /api/v1/cvdeepmatch/{id} for the outcome.

Use retryable / retriesRemaining on the poll response to decide whether to offer a retry.

Request

Responses

202

Retry accepted — the run is processing again.

402

Insufficient credits to fund the retry.

403

Authenticated but not the owner of this run (or missing permission).

404

No run with this id exists for the authenticated client.

409

The run is not in a retryable state — already in progress (RETRY_IN_FLIGHT), not a failed run (RUN_NOT_RETRYABLE), or the retry limit is reached (RETRY_LIMIT_REACHED). No charge, no change.

422

The failure is not retryable (RUN_NOT_RETRYABLE — e.g. an invalid CV), the 24-hour window has expired (RETRY_WINDOW_EXPIRED), or the original inputs are gone (RETRY_INPUTS_GONE). No charge, no change.