// troubleshooting guide · jenkins
Jenkins Build Stuck 'Waiting for Next Available Executor'
- Status
- Workaround available
- platforms:
- Jenkins controller (all OS)
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · jenkins/waiting-for-next-available-executor5 FIXES
// quick answer
The build is queued because no online executor matches it. Check that agents are online with free executors, that the job's label matches a real node, and that pipelines aren't waiting on each other.
Most likely fix: Check executors and agents
How to fix it
// try these in order, the most common fix is first
FIX 1Check executors and agents
- 01Go to Manage Jenkins > Nodes
- 02Look for agents marked offline and reconnect or restart them
- 03Check the number of executors on each node and how many are busy
- 04Hover the queued build to see Jenkins' reason for waiting
Did this fix it?FIX 2Fix the agent label
- 01Open the job configuration or Jenkinsfile and find the label in agent { label '...' } or node('...')
- 02Compare it character by character with the labels under Manage Jenkins > Nodes > <node> > Configure
- 03Correct the typo or add the missing label to an online node
Did this fix it?FIX 3Break pipeline deadlocks
- 01Look for upstream jobs that trigger and wait for downstream jobs on the same limited executors
- 02Add more executors or agents, or don't hold an executor while waiting (e.g. trigger downstream jobs outside a node block)
- 03Remove circular dependencies between jobs
Did this fix it?FIX 4Bring an offline node back
- 01Open the node page and read the offline reason (for example low disk or temp space)
- 02Free the resource or adjust the monitor threshold, then click Bring this node back online
Did this fix it?FIX 5Update plugins and add a timeout
- 01Update plugins in Manage Jenkins > Plugins > Updates
- 02Add a timeout(time: 30, unit: 'MINUTES') option to pipelines so a stuck build fails instead of blocking the queue
- 03Check the Jenkins system log for queue errors
Did this fix it?
SANDBOX · jenkins RUNS IN YOUR BROWSER
Try it: push, review, run CI and merge in a code host and cloud workspace
A hands-on Jenkins-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
The build shows 'Pending - Waiting for next available executor' (or 'Still waiting to schedule task' in the console) and never starts, sometimes even when agents look idle.
Why it happens
- C-01All executors are busy with other builds or the agents are offline
- C-02The job or Jenkinsfile asks for an agent label that no online node has (typo or renamed node)
- C-03Two or more builds wait on each other (deadlock), e.g. a parent job holding an executor while waiting for a child
- C-04The built-in node has 0 executors and no agents are connected
- C-05The node was taken offline by a disk space or other monitor
- C-06Outdated or buggy plugins affecting the queue
// this guide also covers
- jenkins waiting for next available executor
- jenkins build stuck in queue
- jenkins pending waiting for next executor
- still waiting to schedule task jenkins
Still not working?
If Jenkins keeps failing, you're not alone. See every Jenkins 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 usThe same problem in other apps
All export, render & quality loss guides →
Bitbucket Pipelines Build Minutes Exceeded (Bitbucket)
Other Jenkins errors
- Jenkins Build Stuck and Won't Abort
- Jenkins Plugins Failed to Load After Update
- Jenkins Not Starting: 'Job for jenkins.service failed'
- Jenkins java.lang.OutOfMemoryError: Java Heap Space
- Why Is Jenkins So Slow?
- Jenkins 'Scripts Not Permitted to Use Method' Error
- Jenkins GitHub Webhook Not Triggering Build
- Jenkins Git 'Failed to Connect to Repository' Status Code 128