Prefect cloud scheduler bugged out and has schedul...
# ask-community
a
Prefect cloud scheduler bugged out and has scheduled dozens or hundreds of simultaneous scheduled runs for one of our deployments today
z
Which Prefect version are you using?
a
That happened in prefect cloud, not a self run server Our agent runs the latest version of the prefecthq/prefect:2-python3.10 docker image, as of yesterday, but this happened in the prefect cloud so the agent wouldn't be relevant right?
z
Generally. no. Thanks for the info — I was wondering if you were on Prefect 1.
Sorry you ran into an issue though. I’ll ask a Cloud engineer to reach out.
a
Thanks !
z
Are you using automations to schedule runs?
a
Nothing using the API or python triggers or stuff like that, we're using schedules on the deployments
This was the first deployment I tried using an rrule schedule for, maybe I messed it up? Here's the rrule:
FREQ=WEEKLY;INTERVAL=1;BYDAY=FR
Is there a way to limit concurrent runs of the same deployment to 1? This bug is quite problematic for a few reasons, one of which being that triggering dozens or hundreds of simultaneous runs is quite expensive on our execution infrastructure side
NVM found it - I can limit the work pool concurrency
Should I file a bug report on the git repo? This was a pretty dramatic bug and it's important that we get some followup that this won't happen again
z
You are welcome to open an issue — our on call engineer will be in touch with you regardless.
🙏 1
a
👋 @Austin Weisgrau I’m on-call at the moment and will DM for more details.
d
Just out of curiosity, what was the root of the issue?
or the github issue link if some one has made one
a
My bad, I missed this reply! Yes, I can share details: https://github.com/PrefectHQ/prefect/pull/9872