We’ve been having an issue over the past few months where an in-progress Azure Pipelines run/build will end up with a single job stuck at queue priority 1 if a new run begins before it manages to work down the existing queued jobs. The job does eventually start and complete, but only once there are no other jobs in the queue for newer runs.