What is a Priority Job Slot?
A Priority Job Slot is a unit of Transloadit processing capacity used to allocate queued work among customers or IP addresses. A job occupies up to 60 slots according to its estimated resource requirements.
How Priority Job Slots work
Priority Job Slots express scheduler capacity rather than a simple count of active jobs. Each submitted job is assigned slot demand from its estimated processing needs, and the scheduler uses the combined demand when deciding which queued work can run for a customer or address. This places the concept at the admission stage of a media-processing workflow: a few expensive jobs may consume more of the available allocation than many lightweight ones.
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
- 1One job can occupy as many as 60 slots, so concurrency cannot be inferred from the number of Assemblies alone; resource estimates affect how much scheduled capacity each one consumes.
- 2Slots are an allocation mechanism for queued processing, not output threads or media tracks. Their purpose is to apportion compute demand among customers or IP addresses.
- 3A workload can remain below an Assembly submission-rate limit yet still queue for slots when running jobs consume the available processing allocation; the controls measure different pressure.
When Priority Job Slots matter
Account for slot demand when submitting many large or computationally intensive jobs concurrently. Underestimating required capacity can lengthen queue times even when the number of submitted jobs appears modest.
- 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 Priority Job Slots.
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 Priority Job Slots
When Priority Job Slots 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.