Scheduled pipeline doesn't start on schedule, but works fine when manually "played"

GitLab CI/CD
1

  1. I have a scheduled pipeline that is supposed to run every Sunday. I have the interval pattern set to “custom”:
    0 12 * * 0
    and GitLab seems to understand that correctly, tells me correctly when the pipeline is scheduled to run.

  2. The pipeline runs and works perfectly fine when I manually click the “play” button next to it on the pipeline schedules webpage.

  3. Yet, the pipeline does not run when GitLab says it is scheduled to run. Afterwards, it continues to say that the pipeline is scheduled to run, but now in the past. E.g. right now it tells me “Next Run: 20 hours ago”.

So, what the heck? I have absolutely no idea what the issue could be nor any way to attempt to diagnose it. Everything seems fine, and yet the pipeline does not trigger.

Extra info: I do not know if any scheduled pipelines have ever run on our company GitLab instance, so if it is possibly some configuration issue then I can raise that with our IT team. I’d like to have a better idea what might be happening though before sending them off on some wild goose chase.

Gitlab version: GitLab Enterprise Edition v16.3.4-ee
Self-managed instance.

2

Did you find the solution?, I have exactly the same issue… It was working fine until one day it just stopped executing it automatically.

3

Hello! Has anyone come up with a solution? I’ve faced this problem 22 Dec 2024 and can’t fix that :frowning:

4

Here seems to suggest in the pre-requisites section: Scheduled pipelines | GitLab

that would be the first thing to check. After that you may wish to take ownership: Scheduled pipelines | GitLab

Or take a look at troubleshooting section: Scheduled pipelines | GitLab

5

Thank you, but I’ve already read that and it doesn’t help :frowning:
My schedule worked totally fine, but suddenly just stopped working. The schedule is active. If I play it manually - job is running.

It looks like a GitLab bug actually :sweat_smile:
Because this schedule worked great before 22 Dec 2024, nothing was changed in settings, but now when it’s schedule time, job doesn’t start and a column “Next Run” tells that next run will be in the past (for example: “Next Run”: “12 minutes ago”)

6

@All-ice1 Gitlab version?

Generally, as far as I’m aware only latest 3 versions are supported, so:

17.7.1
16.11.10
15.11.13

the OP uses 16.3.4 so should really be upgrading since things could be fixed in later versions. If you have a similar situation you may need to look at upgrading first.