Maximum number of ci pipeline schedules (50) exceeded
The triage-ops pipeline ran into the following error today here:
Maximum number of ci pipeline schedules (50) exceeded
@alinamihaila has identified that this was triggered by Make Quality Report monthly (!2076 - merged) which was then reverted here.
I would like to understand what this means as this is the first time I see the error. Does the limit
refer to too many scheduled automations we have overall, or does it mean we have too many different schedules (cron
definitions), since knowing what the limit is can help us decide how to mitigate it from happening again.
Edited by Jennifer Li