Jobs created through the UI after 15 April 2024 have this enabled by default. When a concurrency limit would otherwise cause a run to be skipped, the run waits instead, for a maximum of 48 hours.
Also called job queueing.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Queueing in context, with comparison tables and the common traps.
Terms in this definition
- LIMIT
Caps how many rows a SQL query gives back. Don't treat what you get as random or representative.
Related terms
- Jobs API 2.2
A release of the REST API for jobs where queueing of runs is the default. Long lists are split into pages using
next_page_token, not a root-levelhas_more. - Maximum concurrent runs
The
max_concurrent_runsjob setting, 1 by default, which limits the number of runs of a job active simultaneously. Extra runs are skipped unless queueing is turned on. - Phase breakdown
Splits a job run's time into phases, for instance queueing or waiting for resources. That makes it clear where the time was spent and what's worth changing.