GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them
No GitLab runner can pick up the job — runners are offline, the job’s tags don’t match any runner, or shared runners are disabled.
Seen on:
GitHub Actions
Meaning
Jobs run only on runners whose tags include all job tags. Disabled shared runners, a stopped self-hosted runner, or protected-branch-only runners also leave jobs pending.
Common causes
- Job tags not matching any runner
- Self-hosted runner offline/stopped
- Shared/instance runners disabled for the project
- Runner limited to protected branches
⚡ Quick fix
- Check Settings → CI/CD → Runners for online runners and tags
- Remove or fix tags in .gitlab-ci.yml
- Enable shared runners or start your runner
Detailed fix by platform
YAML
- yaml
build: tags: [docker] # must match an online runner's tags script: make build
Shell
- yaml
sudo gitlab-runner status sudo gitlab-runner verify
How to diagnose
- Runners — Online list
- Tags — Job vs runner
- Protection — Branch protected?
🔧 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
- No hosted parallelism Azure Pipelines: No hosted parallelism has been purchased or granted
- Resource not accessible by integration GitHub Actions: Error: Resource not accessible by integration (403)
- The process '/usr/bin/git' failed with exit code 128 GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
Other ways to find it
🧠 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026