Today I noticed that a Gitlab scheduled pipeline wasn’t running anymore - it should have automatically. I checked and it wasn’t enabled at all!
At first I thought that somebody else on my team had made a mistake and accidentally disabled the scheduled pipeline. So I enabled the pipeline and manually started it.
Then I went to check if it was running, but instead it wasn’t running and even disabled again!
That’s when I noticed that the scheduled pipeline belongs to a team member that wsan’t part of the team anymore. (Why does a scheduled pipeline need an owner? Because the pipeline needs to run with certain permissions - and when triggered, the pipeline runs with the owner’s permissions).
So I changed the scheduled pipeline’s owner to myself, re-enabled the pipeline and started it. Then the pipeline worked.
And yes, this behavior is documented:
If a pipeline schedule becomes inactive because the original owner is unavailable, you can take ownership.