What is an Encoding Job?
An Encoding Job is the smallest processing unit in Transloadit, such as one video encode or image resize executed on an encoding machine. Despite the historical name, Robot operations are scheduled as Encoding Jobs, including imports, exports, and metadata extraction, not only codec work.
How Encoding Jobs work
Within a Transloadit Assembly, the workflow graph turns applicable processing operations on assets into schedulable work. Dependency edges hold a downstream task until the outputs it consumes are ready, while unrelated branches can progress independently. The job is therefore an execution and capacity concern, whereas the Assembly is the coordinating workflow visible to an integration and the unit at which replays are requested. Status aggregation maps these granular outcomes back to the larger request.
Key facts
- 1One Assembly can produce many jobs when Steps fan out across uploaded files or create several derivatives, so the number of API submissions is not a reliable measure of processing demand.
- 2A failed job can block only the downstream jobs that require its result while independent branches may already be complete; the recovery affordance is replaying the Assembly, which re-runs the workflow as a new Assembly rather than retrying one job.
- 3Job cost and duration vary with input complexity and operation type, not only file size, and a turbo-mode video encode splits into segment jobs that occupy job slots themselves.
When Encoding Jobs matter
Developers estimate job counts when planning workflow capacity, cost, and concurrency. Recovery happens at the Assembly level: a crashed Assembly can be replayed as a new Assembly, so design workflows with the cost of re-running them in mind rather than assuming an individual failed job can be retried in isolation.
Common use cases for platform workflows
These examples cover platform workflows broadly, not specifically Encoding Jobs.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Referencing centrally stored credentials by name instead of sending storage secrets with each request.
Working with platform workflows
This guidance covers platform workflows broadly, not just Encoding Jobs.
A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.
Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.
What you gain
- Reusable workflows separate application intent from processing infrastructure.
- Stable job identifiers and lifecycle events improve observability and recovery.
- Managed queues and workers let products scale without embedding every media tool.
What it costs
- Synchronous responses are simple but keep connections open while long work executes.
- Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
- Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.
Before production
- 1Define authentication, authorization, idempotency, retries, and terminal error behavior.
- 2Observe queue time, execution time, callbacks, and partial results with stable identifiers.
- 3Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.