What is a Job Slot Limit?
A Job Slot Limit is a configurable per-customer Transloadit value that governs how many Encoding Jobs can use the Live Queue. Jobs beyond that capacity move to the Batch Queue.
How Job Slot Limits work
The limit is a weighted concurrency budget rather than a simple count of files or Assemblies. Each active Robot job claims a service-specific number of slots, and the total is evaluated for the workspace within a processing region. When priority capacity is occupied, additional live work waits outside the shared fast lane until slots return; steps may also be assigned deliberately to batch processing. Planning therefore uses the mix and duration of operations, not upload volume alone.
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
- 1Robot types have different slot claims, so the same limit can admit many lightweight image operations but far fewer simultaneous video encodes.
- 2Priority and batch slot allowances are applied per processing region; traffic distribution can therefore change observed concurrency without changing the plan value.
- 3Current queueing separates capacity overflow into backup queues, while a step-level queue setting can intentionally send nonurgent work to the shared Batch Queue.
When Job Slot Limits matter
Capacity planning should set the limit around expected concurrency and the latency required by urgent work. A low limit increases queueing, while a high one may allocate capacity that is rarely needed.
- 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 Job Slot Limits.
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 Job Slot Limits
When Job Slot Limits are 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.