What is Assembly Status?
Transloadit Assembly Status is a JSON-formatted endpoint describing an Assembly. It includes its identifier, uploads, results, execution duration, and information needed to locate result files.
How Assembly Status works
The status representation is the canonical snapshot of a processing job at the time it is requested. It brings together lifecycle state, timing, input records, Step outputs, errors, and result locations in a machine-readable response. Intermediate snapshots can change as branches finish, whereas terminal snapshots support durable result ingestion. A backend typically normalizes this document into its own job model and retains identifiers for support diagnostics.
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.
Key facts
- 1Uploads and generated results are separate collections in the response, allowing clients to distinguish submitted source records from derivative files produced by Steps.
- 2Result entries are organized by Step name, so consumers should bind to the intended workflow branch rather than assume the first returned file is the desired asset.
- 3Polling clients need to recognize terminal success and failure states explicitly; the presence of partial metadata or some result files does not prove the whole graph succeeded.
When Assembly Status matters
Query this endpoint to inspect completion, collect result URLs, or diagnose a failed Step. Do not treat an unfinished response as final, and handle terminal failure states before consuming outputs.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Applying credentials, quotas, retries, and error policies consistently across integrations.
Working with platform at scale
Guidance that holds across every platform term in this glossary, not just Assembly Status.
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.
Answer these 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.
How Transloadit helps with Assembly Status
When Assembly Status is relevant to your workflow, you can hand the surrounding platform work to Transloadit instead of maintaining the processing stack yourself. Transloadit models file workflows as reusable Assembly Instructions. Upload, import, processing, AI, storage, delivery, status updates, and error handling can be composed without operating the underlying media tools yourself.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.