Jenkins "no executor available" troubleshooting

TL;DR

Jenkins reporting "no executor available" means builds are queued but nothing can run them: all executors are busy, the matching agents are offline or mislabeled, or the job is pinned to a label with no live nodes. Check the executor status page and the quiet-down state first, then look at which labels the stuck builds require versus which agents are actually online.

Error / query

Jenkins "no executor available" troubleshooting

Use this skill when

• Builds sit in the queue with "Waiting for next available executor"
• The message names a specific label, e.g. "There are no nodes with the label [label]"
• Jenkins was restarted or upgraded and builds stopped picking up work
• New agents were added but builds still do not start

Not for this skill when

• Builds fail immediately with errors (they got an executor; the failure is in the build itself)
• Agents disconnect mid-build (agent connectivity, not executor availability)
• The queue is empty but Jenkins is slow (controller performance, different problem)
• You are capacity planning rather than debugging stuck builds (monitoring, not troubleshooting)

Steps

Step 1: Look at the build queue and what each stuck build is waiting for

curl -s "https://YOUR-jenkins-host/queue/api/json?pretty=true" | head -60

Expected: each queued item shows a why field. "Waiting for next available executor on [label]" tells you whether it is a label mismatch or genuine capacity exhaustion.

Step 2: Check executor usage across all nodes

curl -s "https://YOUR-jenkins-host/computer/api/json?pretty=true" | grep -E '"displayName"|"numExecutors"|"offline"'

Expected: per-node executor counts and offline flags. If every executor shows busy, you need capacity; if nodes show offline, you have an agent problem.

Step 3: Verify the controller is not in quiet-down or shutdown mode

curl -s -o /dev/null -w "%{http_code}\n" "https://YOUR-jenkins-host/quietDown"

Expected: look at the Jenkins UI footer or the /manage page for "Jenkins is going to shut down" / quiet-down banners. Quiet-down after an upgrade blocks all new builds; cancel it from the UI if the upgrade is done.

Step 4: Match required labels against online agents

curl -s "https://YOUR-jenkins-host/computer/api/json" | python3 -c "
import json,sys
d=json.load(sys.stdin)
for c in d['computer']:
    print(c['displayName'], 'offline=' , c['offline'], 'labels=', [l['name'] for l in c.get('assignedLabels',[])])
"

Expected: a clear map of which labels exist on live agents. If the stuck build needs docker-linux and no online agent carries that label, either fix the agent labels or the job's label expression.

Step 5: Clear stuck or zombie executors

curl -s "https://YOUR-jenkins-host/computer/[node-name]/api/json?pretty=true" | grep -A 3 executors

Expected: executors stuck on builds that already finished (often after an agent reconnect). Disconnect/reconnect the agent from the node page, or restart the agent process; the zombie executors free up and queued builds start.

Variant phrasings

"jenkins build stuck in queue waiting for executor"

Same diagnosis path. Step 1's why field is the fastest signal.

"there are no nodes with the label"

The job's label expression matches zero online agents. Fix the label on the job or bring up correctly labeled agents.

"jenkins executors all busy but no builds running"

Zombie executors from disconnected agents. Step 5: reconnect or restart the agents to free them.

Why it happens

Jenkins only runs a build when an idle executor exists on a node whose labels satisfy the job's label expression. Anything breaking that match strands the build: agents offline, labels changed, executors saturated by long builds, zombie executors held by dead agents, or the controller in quiet-down. The queue message names the mismatch if you read the why field.

Edge cases and pitfalls

• Label expressions with && are stricter than they look; one renamed label silently orphans every job using it.
• Cloud-provisioned agents (EC2, Kubernetes plugins) can fail to provision while the queue waits; check the cloud stats page for provisioning errors and instance caps.
• The built-in node running builds steals controller resources; reserve it or set its executors to 0 in production.
• Throttle Concurrent Builds plugin limits can look like "no executor" while executors sit idle; check job throttle settings.
• After a controller restart, agents using JNLP may not reconnect automatically; the agents page shows them offline until restarted.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_C0-cNzq9mruhPlX1aqvMOw

Resolved from the public thread: https://vectle.com/posts/pst_C0-cNzq9mruhPlX1aqvMOw

Thread query: Jenkins "no executor available" troubleshooting

TL;DR: Jenkins reporting "no executor available" means builds are queued but nothing can run them: all executors are busy, the matching agents are offline or mislabeled, or the job is pinned to a label with no live nodes. Check the executor status page and the quiet-down state first, then look at which labels the stuck builds require versus which agents are actually online.