GitLab Pipeline Stuck on Pending

Share
Ongoing Self-managed or GitLab.com Updated November 13, 2026Based on 4 user reportsHow we research

Quick answer

A pending job means no runner is able to take it. Check that an online runner matches the job tags, is allowed to run untagged or protected jobs, and that you still have compute minutes.

Most likely fix: Check which runners the project can use

How to fix it

Try these in order — the most common fix is first.

  1. 1. Check which runners the project can use

    1. Go to Settings > CI/CD > Runners.
    2. Confirm at least one runner shows a green online dot.
    3. Offline runners: restart with sudo systemctl restart gitlab-runner and check journalctl --unit=gitlab-runner.service -n 100 --no-pager.
    Did this fix it?
  2. 2. Match job tags and runner tags

    1. Compare the tags: list in the job with the tags on the runner.
    2. Either remove the tags from the job or edit the runner and tick "Run untagged jobs".
    Did this fix it?
  3. 3. Check protected and locked settings

    1. Edit the runner and see if "Protected" is on; then only protected branches and tags can use it.
    2. Locked runners are tied to a single project, so enable them for yours.
    Did this fix it?
  4. 4. Check shared runner quota and verification

    1. On GitLab.com open Settings > Usage Quotas to see compute minutes.
    2. Free accounts must add a credit card (a $1 authorization, not charged) before shared runners work.
    3. Buy more minutes ($10 per 1,000) or register your own runner.
    Did this fix it?
  5. 5. Know when GitLab drops the job

    1. Pending jobs with no matching runner fail after 1 hour; with matching but busy runners after 24 hours.
    2. Retry the pipeline once the cause is fixed.
    Did this fix it?

Symptoms

Job shows "This job is stuck because the project doesn't have any runners online assigned to it" or sits in Pending for a long time.

Why it happens

  • Job tags in .gitlab-ci.yml do not match any online runner
  • Runner is offline or the gitlab-runner service stopped
  • Runner set to tagged jobs only while the job has no tags
  • Runner is protected-only but the branch is not protected
  • Out of compute minutes on GitLab.com shared runners
  • No credit card on file for free GitLab.com shared runners

This guide also covers

  • gitlab pipeline stuck pending
  • this job is stuck because the project doesn't have any runners online
  • gitlab ci job pending forever
  • gitlab runner tags stuck

Still not working?

If GitLab keeps failing, you're not alone. See every GitLab problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other GitLab errors

All 11 GitLab errors and fixes →