Skip to main content
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 failed or partial_failure (400 for any other status).
  • The file’s detection session must still exist (404 otherwise — see POST /file/{id}/redetect if it expired).
  • If a job for this session is already active, waiting, or delayed in 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: true instead of retrying, since there is nothing left to re-read.
On success, the file’s status is set back to 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

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Path Parameters

fileId
string<uuid>
required

The failed file to retry.

Response

File re-queued for processing, or (when the original object is no longer in storage) a requiresReupload notice instead of a retry

status
string
Example:

"success"

message
string
data
object