So I recently noticed that a schedule I have set up for a pipeline has not been running for over a week. This schedule is supposed to run four times a day to check an integration for schema updates, create a new branch if there is any changes, and finally create a merge request for that branch.
This has been running flawlessly until a week ago, and now when try to manually trigger the schedule, no errors no nothing. I am aware that the docs state that minimum required role is Developer for a user to trigger schedules, and that no errors would show if the account does not have the Developer role - however, I am listed as the owner of the repository and I believe that should be sufficient? I can do all other necessary tasks git-wise that I need to do (merge branches to default branch etc).
When I access the CI/CD settings, I see a error stating the following;
There was an error fetching the environments information.
Other than that I see nothing in that would indicate that scheduled pipelines would not work.
What are you seeing, and how does that differ from what you expect to see?
I expect to see scheduled pipelines triggered according to cron setup, but they do not run. Not manual triggered schedules either.
What version are you on? Are you using self-managed or GitLab.com?
Gitlab.com SaaS paid tier (org account)
What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
- Verified that pipeline runs normally for all branches (push, merge etc)
- I have verified that I am not using group runners, but rather gitlabs shared runners.