// troubleshooting guide · azure devops

Azure DevOps Pipeline Stuck in Queue (Waiting for an Available Agent)

Status
Ongoing
platforms:
Web (Azure Pipelines)
updated:
November 16, 2026
reports:
5
Method
how we research
Share

RUNBOOK · azure-devops/pipeline-stuck-queued4 FIXES

// quick answer

A queued run waits because every parallel job or agent is busy, no agent matches its demands, or a stage waits for approval. Check Project settings > Parallel jobs and your agent pool first.

Most likely fix: Check parallel job usage

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Check parallel job usage

    1. 01Go to Project settings > Parallel jobs (or https://dev.azure.com/{org}/_settings/buildqueue?_a=concurrentJobs)
    2. 02Choose View in-progress jobs for the hosted or self-hosted pool
    3. 03If it says 'Currently running X/X', cancel an old run or buy another parallel job
    Did this fix it?
  2. FIX 2Check agents and demands

    1. 01Open https://dev.azure.com/{org}/_settings/agentpools and select the pool > Agents
    2. 02Make sure agents are online and not all busy
    3. 03Compare the pipeline's demands with each agent's Capabilities tab and remove or fix mismatched demands
    Did this fix it?
  3. FIX 3Look for pending approvals

    1. 01Open the run and check whether a stage shows 'Waiting' for approval or checks
    2. 02Approve it, or adjust the environment's Approvals and checks
    Did this fix it?
  4. FIX 4Rule out an outage and cancel stuck runs

    1. 01Check status.dev.azure.com for pipeline degradation in your region
    2. 02Cancel runs stuck for hours (az pipelines runs commands in the Azure DevOps CLI can help)
    3. 03If hosted jobs stay stuck, open a support ticket
    Did this fix it?

Symptoms

The run stays at 'Queued' or 'Waiting for an available agent', or shows 'The agent request is not running because all potential agents are running other requests. Current position in queue: 1'.

Why it happens

  • C-01All parallel jobs in the organization are in use (they are shared by every pipeline)
  • C-02All agents in the pool are busy or offline
  • C-03Pipeline demands don't match any agent's capabilities
  • C-04A stage is waiting for an approval or check
  • C-05Hosted capacity shortage or an Azure DevOps incident
  • C-06Orphaned job requests stuck in the pool

// this guide also covers

  • azure devops pipeline stuck queued
  • waiting for an available agent azure devops
  • azure pipelines not starting

Still not working?

If Azure DevOps keeps failing, you're not alone. See every Azure DevOps problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Azure DevOps Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Azure DevOps errors

All 12 Azure DevOps errors and fixes →