GitLab pipeline schedule not running (owner, variables, disabled) in CI
A GitLab pipeline schedule runs as its owner, so if that user loses access or is deactivated the schedule stops. It also silently does nothing if the schedule is toggled inactive, or if job rules exclude $CI_PIPELINE_SOURCE == "schedule".
What this error means
A GitLab scheduled pipeline that used to run stops appearing, or it runs but every job is skipped because no job matches the scheduled pipeline source.
# .gitlab-ci.yml - this job never runs on a schedule:
nightly:
script: ./nightly.sh
rules:
- if: '$CI_PIPELINE_SOURCE == "push"' # excludes "schedule"Common causes
The schedule owner lost access or is inactive
Scheduled pipelines run with the owner permissions; if that account is deactivated or loses project access, the schedule stops.
Rules exclude the schedule source
If no job rules match $CI_PIPELINE_SOURCE == "schedule", the scheduled pipeline runs with no jobs, or the schedule is simply toggled inactive.
How to fix it
Reassign ownership and add schedule variables
- Under CI/CD > Schedules, confirm the schedule is Active and take ownership if needed.
- Add any required variables to the schedule definition.
- Ensure at least one job matches the schedule source.
nightly:
script: ./nightly.sh
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule"'Take ownership when an owner leaves
A maintainer can take ownership of an orphaned schedule so it runs with valid permissions again.
How to prevent it
- Keep schedules owned by an active account with access.
- Match jobs to
$CI_PIPELINE_SOURCE == "schedule". - Set schedule variables in the schedule, not only defaults.