Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline
A Jenkins build is queued because no executor with the required label is free or the agent is offline.
Waiting for next available executorStill waiting to schedule taskThere are no nodes with the labelis offline Jenkins agentWaiting for next available executor on Meaning
Check Manage Jenkins → Nodes. An agent may be offline (disk space, network, SSH/JNLP failure), have all executors busy, or not match the label in agent { label 'x' }. The queue message explains which. Bring the agent online or fix the label.
Common causes
- Agent offline (crashed, network, disk space low, credentials)
- Label in the Jenkinsfile matches no node
- All executors busy
- Node marked temporarily offline by a health check (low disk or swap)
- Cloud agents not provisioning
⚡ Quick fix
- Open Manage Jenkins → Nodes and relaunch the agent
- Check the label spelling in
agent { label '…' } - Free disk space or raise executor count
Detailed fix by platform
Jenkins
- Hover the queue item for "because" text; node log is under Nodes → agent → Log
Code examples
Pin a label
pipeline {
agent { label 'linux && docker' }
stages { stage('Build') { steps { sh 'make' } } }
}How to diagnose
- Node — Online?
- Label — Matches a node?
- Capacity — Executors free?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Container exceeded memory limit Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137
- Could not find credentials entry Jenkins: ERROR: Could not find credentials entry with ID 'github-token'
- No such DSL method Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps
Most viewed in CI/CD
- The process '/usr/bin/git' failed with exit code 128 GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
- Resource not accessible by integration GitHub Actions: Error: Resource not accessible by integration (403)
- ComparisonError: manifest generation failed Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 25 Oct 2026