Active Ci::PipelineSchedule have a nullified `next_run_at`
It turned out that a few Ci::PipelineSchedule exists with
active = true and
next_run_at IS NULL (See https://gitlab.com/gitlab-com/infrastructure/issues/2396#note_36518030).
This should not happen.
We should figure out why this happened and add a new patch to rescue those cases.
Steps to reproduce
What is the current bug behavior?
Some pipeline_schedules are active but
What is the expected correct behavior?
All active pipeline_schedules must have
Output of checks
This bug happens on GitLab.com
- ZD: https://gitlab.zendesk.com/agent/tickets/80289
- #32790 (comment 36353999)