/errors/gitlab-ci/job-stuck-no-runners
GitLab CI: This job is stuck because the project doesn't have any runners online assigned to it
The commands on this page have not been executed by our verification runner yet.updated 2026-10-20
- tool
- GitLab CI/CD
- exit code
- 0
- versions
- GitLab 16+
- os
- any
A GitLab job waits in the pending state until a runner picks it up. When GitLab can see that no runner is able to take it, the job page shows This job is stuck because the project doesn't have any runners online assigned to it. (or a variant mentioning tags). Nothing is wrong with the job's script; the problem is the matching between the job and the runners.
How a runner is chosen
A runner can take a job only if all of these hold:
| Condition | Where to check |
|---|---|
| The runner is available to the project (project, group or instance runner) | Settings > CI/CD > Runners |
| The runner is online and not paused | the runner list, green dot |
| The runner has every tag the job lists | job tags: in .gitlab-ci.yml, runner tags in its settings |
| For untagged jobs: the runner has "Run untagged jobs" enabled | runner settings |
| For protected branches or tags: the runner is not restricted, or is protected | runner settings |
Fix tag mismatches
build:
tags: [docker, linux] # the runner must have both tags
script:
- make buildRemove tags that no runner has, or add them to the runner.
Register a runner
gitlab-runner register --url https://gitlab.example.com --token "$RUNNER_AUTH_TOKEN" --executor docker --docker-image alpine:3.22
gitlab-runner verifyCreate the runner (and its authentication token) first in Settings > CI/CD > Runners > New project runner, then register it on the machine.
Sources
Related pages
compare · gitlab-ciGitHub Actions vs GitLab CI/CD: concepts and syntax side by sideGitHub Actions runs event-triggered workflows built from reusable actions; GitLab CI uses one .gitlab-ci.yml with stages, rules and includes. How they map.cheat sheets · github-actionsGitHub Actions cheat sheet: triggers, jobs, matrix, outputs and cachingGitHub Actions cheat sheet: triggers, jobs and needs, matrix builds, if conditions, step and job outputs, secrets and env, caching, artifacts, contexts.glossary · argo-cdWhat is GitOps?GitOps keeps the desired state of apps and infrastructure in Git, and an agent such as Argo CD or Flux keeps the cluster matching it and reverts drift.