Share via

Azure DevOps Pipeline jobs are queued, and we have idle agents, but none are being run

Andrew White 0 Reputation points
2026-03-11T20:52:08.9533333+00:00

This started around 11am Eastern today. We have a number of pipelines that are triggered off of Pull Requests and are normally processed by a Microsoft-hosted Agent pool (max parallelism 1). However, now the jobs are just sitting in the queue, and our agent is sitting idle not having run anything in over 5 hours.

Our agent pool and pipelines jobs haven't changed, and I don't see any capability requirements failing.

The first job in our agent queue has this message: "This agent request is not running yet. Current position in queue: 1. Current parallelism: 0. Max Parallelism for parallelism type 'Microsoft-Hosted Private': 1"

Azure DevOps
{count} votes

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.