Unexpected Pipeline Trigger Upon Activation
Scheduled pipelines that have been inactive are immediately triggering a run upon being set to active, even when the defined custom schedule (cron) is set for a future time. The pipeline should remain idle until the next scheduled interval.
Steps to Reproduce Create a scheduled pipeline with a specific custom cron (e.g., 0 0 * * * for midnight).
Deactivate the schedule (set to Inactive).
Wait until a time that does not match the cron expression.
Reactivate the schedule (set to Active).
Observe that the pipeline triggers a run immediately.
Current Behavior The pipeline starts a new job execution the moment the status is toggled to "Active," regardless of the cron configuration.
Expected Behavior The pipeline should enter a "waiting" state and only trigger at the next occurrence defined by the schedule.
Environment Information GitLab Installation: Self-Hosted/Self-managed
GitLab Version: 18.7