Changes / GitLab / Jobs not being picked up/stuck pending
GitLab: Major incident: Jobs not being picked up/stuck pending
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: degradation (model (Jev), 79%)Changed Detected Source: status.gitlab.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Jobs not being picked up/stuck pending
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-18 11:03 UTC
Before: not present
After: 2026-05-18 12:41 UTC
Before: not present
After: CI/CD, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners on Windows
Before: not present
After: We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
Before: not present
After: We're seeing improvements in job queueing after additional runner allocations to the runner resource pool. We will continue to monitor until the the jobs are getting picked up at normal rates. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
Before: not present
After: We've continued to monitor the job queues following the additional provisioning of runners to the resource pool and we observe that the queueing is back to normal. This incident is moved to resolved. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Jobs not being picked up/stuck pending (this change) | Major incident |