GitLab CI: "This job is stuck because the project doesn't have any runners online assigned to it". How do I get the job to run?

Cause: The pipeline job is pending because GitLab cannot find an online runner that is allowed to take it. Matching depends on runner type, status, tags and settings. Common reasons: no runner is available to the project at all (no instance, group or project runner enabled), the runner process is offline, the job's tags are not all present on any runner, the job has no tags but the runners have "Run untagged jobs" turned off, or the runner is marked Protected while the job runs on an unprotected branch or tag. Fix: 1. Open Settings > CI/CD > Runners in the project and see which runners are available and whether any show as online. On GitLab.com, check that instance runners are enabled for the project if you want GitLab-hosted ones. 2. If your own runner is offline, start or restart the gitlab-runner service on its host and check its logs, and confirm it can reach the GitLab URL and its token has not been revoked. 3. Compare tags: a runner is chosen only if it has all the tags listed in the job's tags: keyword. Remove tags the job does not need, or add them to the runner. 4. For jobs without tags, edit the runner and enable "Run untagged jobs", or add tags to the job. 5. If the runner is Protected, run the job on a protected branch or tag, or deliberately unprotect the runner only if the security trade-off is acceptable. 6. If no runner exists, register one (project, group or instance level) using the documented gitlab-runner registration flow. Verify: the job leaves "pending", a runner picks it up, and the runner's status shows it online and active. Sources: https://docs.gitlab.com/ci/runners/configure_runners/ https://docs.gitlab.com/ci/runners/