Skip to main content

Job states

A job normally moves through these states:
completed, failed, and canceled are terminal states. Stop polling when you receive one of them. The progress field is a percentage from 0 to 100, not an estimate of remaining time.

Poll for results

Call Get job every five seconds. The response includes Retry-After: 5. If a request returns 429, honor Retry-After before trying again. Successful HTTP status does not imply successful processing: a 200 job response may contain status: "failed". Inspect both the HTTP status and the job’s status.
This release uses polling. Webhook callbacks are not currently supported.

Submit another job

Each accepted POST /v1/subtitles request creates a new job, even when its input is identical to an earlier request. Each successful job is billed separately. Save the returned job ID and poll its status instead of submitting again. If a submission times out or its response is lost, check your recent jobs in the console before retrying: the original job may already exist. To retry a failed or canceled job, fix the underlying issue and submit another request.

Cancel a job

Call Cancel job for a queued or processing job. It changes to canceled and releases the reservation. If processing has already reached a terminal state, cancellation returns that existing state. Completed jobs remain billed.

Retention and timeouts

Result files expire 24 hours after completion. Check expires_at and save all outputs to your own storage. Before expiry, fetch the job again to obtain current download URLs. After expiry the job can remain completed, but file URLs are null; fetching it again does not restore expired files. Source ingestion, transcription and caption preparation have a ten-minute deadline. Prepared jobs waiting for renderer capacity time out after 30 minutes. Assigned renders have a one-hour ceiling. A processing failure or timeout releases the job’s reserved credit; it does not automatically submit a replacement.