What is Assembly Execution Progress?
Transloadit Assembly Execution Progress estimates an Assembly’s completion in real time. Percentages are calculated from its Steps and may describe overall execution or an individual file.
How Assembly Execution Progress works
Execution progress aggregates how far scheduled work has advanced across a graph whose branches may differ greatly in cost. The displayed value is derived from Step and file activity rather than from a simple wall-clock countdown, so it may advance unevenly. Overall progress summarizes the job, whereas file-level progress can expose a slow or blocked item. Interfaces consume the estimate for feedback while status data remains the authority on completion.
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
- 1A late transcoding Step can account for much more real time than an earlier metadata Step, so equal percentage increments do not imply equal remaining durations.
- 2Parallel branches and files may update independently; aggregation can appear to pause while a costly operation runs even though the Assembly is still healthy.
- 3Progress should reach a terminal interpretation only alongside Assembly status, because a failed or canceled branch is not equivalent to successful completion at 100%.
When Assembly Execution Progress matters
Display these estimates when users need feedback during long processing jobs. Treat the percentage as an estimate rather than elapsed time, because Steps can have unequal or unpredictable durations.
- 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 Execution Progress.
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 Execution Progress
When Assembly Execution Progress 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.