Retry a failed royalty file
File
Retry a failed royalty file
Re-queues a failed or partial_failure file for processing on the
POST
Retry a failed royalty file
This endpoint requires authentication. Include your Bearer token in the Authorization header.
Description
same detection session, reconstructing the original job (source, accounting/sale period, schema, delimiter) rather than requiring a fresh upload. Guards before re-queueing:- The file must currently be
failedorpartial_failure(400 for any other status). - The file’s detection session must still exist (404 otherwise — see
POST /file/{id}/redetectif it expired). - If a job for this session is already
active,waiting, ordelayedin one of the processing queues, the retry is refused (409) rather than double-queueing. - The original object must still be present in cloud storage;
otherwise this returns 200 with
data.requiresReupload: trueinstead of retrying, since there is nothing left to re-read.
processing and its
prior error/progress metadata is cleared.
Authorization: admin or higher (this route has no explicit RBAC
entry, so it falls back to the platform default of admin or
higher) plus the royaltyAccess feature flag.
Code Examples
Authorizations
JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"
Path Parameters
The failed file to retry.