GitLab scheduled pipeline not running: inactive schedules and other causes
Short answer
A GitLab pipeline schedule runs as its owner, on the latest commit of its target branch or tag, and most failures leave no pipeline and no error. If the schedule shows Inactive, its owner was usually blocked, removed or moved below the Developer role: a Maintainer selects Take ownership, then edits the schedule and turns Activated back on. If it's active but nothing appears, check that workflow:rules and job rules allow $CI_PIPELINE_SOURCE == "schedule", that the target branch still exists, and that the owner may push or merge to it if it's protected. Selecting Run helps: a manual run creates the pipeline with your permissions, so if it works, look at the owner's access to the branch. On GitLab.com Free, a schedule runs at most once an hour.
A schedule in Build › Pipeline schedules shows a Next Run time, the time passes, and no pipeline appears. GitLab doesn’t fail loudly here: in most cases it creates no pipeline and shows no error. Here’s what to check in GitLab 19.5, most common first.
The schedule is Inactive
GitLab deactivates a schedule when its owner can no longer create pipelines in the project: blocked, removed from the project, or moved below the Developer role. It emails the project’s direct Owners and Maintainers that the schedule “is deactivated and cannot run”; members who get their role only through a group get no email.
To restart it:
- As a Maintainer or Owner, select Take ownership next to the schedule. It now runs with your permissions.
- Select Edit, turn on Activated, and select Save changes.
Taking ownership alone doesn’t reactivate the schedule. A schedule someone turned off with Activated shows Inactive too.
Active, but nothing runs: select Run
Next to the schedule, select Run (the play button). GitLab replies “Successfully scheduled a pipeline to run” and queues it. Then look in Build › Pipelines:
- No pipeline appears: the problem is in the project. Check the rules and the branch. If the schedule turns Inactive instead, its owner lost access: see above.
- The pipeline runs: a manual run creates the pipeline with your permissions, not the owner’s, so check the owner’s access to a protected branch, then the timing.
Rules filter out the schedule
A scheduled pipeline has $CI_PIPELINE_SOURCE set to schedule. If workflow:rules don’t match that, or no job’s rules do, GitLab creates no pipeline at all: no failed pipeline, nothing on the schedule. Other rules that leave nothing are in Pipeline will not run for the selected trigger.
workflow:
rules:
- if: $CI_PIPELINE_SOURCE == "schedule"
- if: $CI_PIPELINE_SOURCE == "merge_request_event"
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
nightly-tests:
rules:
- if: $CI_PIPELINE_SOURCE == "schedule"
script:
- make test-all
- Jobs only in
.preor.postdon’t count: GitLab doesn’t create a pipeline with nothing else in it. - Several schedules on one branch? Match each one’s description, which
$CI_PIPELINE_SCHEDULE_DESCRIPTIONholds since GitLab 17.8:if: $CI_PIPELINE_SCHEDULE_DESCRIPTION == "Nightly tests". A variable in each schedule’s form, such asTASK: nightly, works where Settings › CI/CD › Variables › Minimum role to use pipeline variables allows it; projects in newer GitLab.com groups default to no one. [skip ci]doesn’t apply. A scheduled pipeline runs even when the latest commit says to skip CI; more in how to skip a GitLab CI pipeline.rules:changesis always true in a scheduled pipeline, which has no push to compare, so those jobs run every time. Addcompare_toto compare with another branch instead; compared with the schedule’s own branch nothing changed, so the job wouldn’t run. See GitLab CI rules:changes not working.
The branch is gone or protected
- The target branch or tag was deleted or renamed, or it has no
.gitlab-ci.yml. GitLab creates nothing. Edit the schedule and pick the target again. - The branch is protected. The owner must be allowed to push or merge to it, or, for a protected tag, to create protected tags. GitLab checks at every run, so a tightened rule stops the schedule silently while it still shows Active. Take ownership as someone who’s allowed, or change the rule: see protected branches.
- The project is archived, or in an archived group, or it or its group is marked for deletion. Schedules don’t run there. On GitLab.com Free, a private namespace over the five-user limit is read-only and can’t run pipelines at all.
An invalid .gitlab-ci.yml is the common case that leaves a trace: a failed pipeline with the error. Fix it as in GitLab CI “configuration is invalid”.
It runs late, or less often
- Schedules start on GitLab’s clock. A background worker queues due schedules: by default every 10 minutes on GitLab Self-Managed, at 3, 13, 23 minutes past the hour and so on, and every 5 minutes on GitLab.com. On Self-Managed, a schedule for 09:00 starts at 09:03.
- GitLab.com caps each schedule: 24 pipelines a day on the Free tier, so at most once an hour, and 288 on paid tiers, every 5 minutes. A
*/15 * * * *schedule on Free runs hourly. - The cron runs in the schedule’s Cron timezone, set in its form, not in yours or the server’s.
- The pipeline started, but its jobs wait. That’s a runner problem: see jobs stuck pending.
Creating a schedule needs the Developer role and a verified primary email address. GitLab.com allows 10 schedules per project on Free and 50 on paid tiers; GitLab Self-Managed allows 10 by default.
On your phone
The schedule itself, with its owner, target and Activated setting, lives in Build › Pipeline schedules in GitLab in a browser. Once a scheduled pipeline runs, it’s a pipeline like any other: MergeBell shows its job logs live, and Retry reruns a failed job on the free tier, with your permissions. More in how to retry a failed GitLab pipeline.
Frequently asked questions
Why is my GitLab scheduled pipeline not running?
Usually one of four reasons: the schedule is inactive because its owner lost access, workflow:rules or job rules don't allow scheduled pipelines, the target branch was deleted or is protected against the owner, or the project is archived. Most of these leave no pipeline and no error. If the schedule is active, select Run next to it: a manual run creates the pipeline with your permissions, so if it works, look at the owner's access to the branch, then at the timing.
Why did my GitLab pipeline schedule become inactive?
GitLab deactivates a schedule when its owner can no longer create pipelines in the project, for example after being blocked, removed from the project or moved below the Developer role, and emails the project's direct Owners and Maintainers. To restart it, a Maintainer or Owner selects Take ownership in Build › Pipeline schedules, then edits the schedule, turns on Activated and saves. Taking ownership alone doesn't reactivate it.
How do I run a GitLab job only in scheduled pipelines?
Give the job rules: - if: $CI_PIPELINE_SOURCE == "schedule". If the file has workflow:rules, they must allow scheduled pipelines too, or GitLab creates no pipeline at all. To tell several schedules apart, match $CI_PIPELINE_SCHEDULE_DESCRIPTION, the schedule's description, available since GitLab 17.8. Schedule variables work too where the project lets you use pipeline variables; projects in newer GitLab.com groups don't by default.
Why does my GitLab schedule run late or only once an hour?
GitLab queues due schedules with a background worker, every 10 minutes by default on GitLab Self-Managed, at 3, 13 and 23 minutes past the hour and so on, and every 5 minutes on GitLab.com. GitLab.com also caps each schedule at 24 pipelines a day on the Free tier, so once an hour, and 288 on paid tiers. The cron runs in the schedule's own Cron timezone.
Does [skip ci] stop a GitLab scheduled pipeline?
No. Scheduled pipelines ignore [skip ci] in the commit message. To pause a schedule, edit it and clear Activated, or delete it.
Sources
- GitLab docs — Scheduled pipelines
- GitLab docs — Run jobs for scheduled pipelines
- GitLab docs — Maximum scheduled pipeline frequency
- GitLab docs — GitLab.com CI/CD settings
- GitLab docs — rules:changes
- GitLab source — the schedule runner (run_pipeline_schedule_worker.rb)
Checked against these pages on 5 November 2026. GitLab changes quickly — if something here no longer matches, tell us and we will fix it.
Do this from your phone with MergeBell
Free for the whole review loop: the To-Do inbox, diffs and line comments, approve and merge, pipelines with retry, and push alerts for your To-Dos. Works with gitlab.com and self-managed GitLab 16.0+.
Get MergeBell for iPhoneGet MergeBell for Android
On the App Store for iOS 26 or later and on Google Play for Android 12 or later. An independent app, not affiliated with GitLab Inc.