This job is stuck because you don't have any active runners CI/CD Origin: Build & delivery Last updated 14 Oct 2026

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.

Exact message you may see This job is stuck because you don't have any active runnersThis job is stuck because the project doesn't have any runners online assigned to itpending stuck
Explore the map of this error Full error map →
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

  1. Check Settings → CI/CD → Runners for online runners and tags
  2. Remove or fix tags in .gitlab-ci.yml
  3. Enable shared runners or start your runner

Detailed fix by platform

YAML

  1. yaml
    build:
  tags: [docker]   # must match an online runner's tags
  script: make build

Shell

  1. yaml
    sudo gitlab-runner status
sudo gitlab-runner verify

How to diagnose

  1. Runners — Online list
  2. Tags — Job vs runner
  3. 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:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

execution took longer than 1h0m0s — GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds (CI/CD)execution took longer…No hosted parallelism — Azure Pipelines: No hosted parallelism has been purchased or granted (Azure)No hosted parallelismNo space left on device (runner) — GitHub Actions: System.IO.IOException: No space left on device — the runner's disk is full (CI/CD)No space left on devi…Pipeline filtered out by workflow:rules — GitLab CI: No pipeline created — pipeline filtered out by workflow:rules / "The rules configuration prevented any jobs from being added to the pipeline" (CI/CD)Pipeline filtered out…Resource not accessible by integration — GitHub Actions: Error: Resource not accessible by integration (403) (CI/CD)Resource not accessib…runner registration token invalid — GitLab CI: ERROR: Registering runner... failed runner=abc status=couldn't execute POST against https://gitlab.com/api/v4/runners: 403 Forbidden (CI/CD)runner registration t…The process '/usr/bin/git' failed with exit code 128 — GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128 (CI/CD)The process '/usr/bin…The runner has received a shutdown signal — GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled (CI/CD)The runner has receiv…This job …

Explore the map of this error Full error map →

🧠 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.