We're seeing duplicate flow runs scheduled in Prefect Cloud. This flow id, for example, is currently duplicated: 5842f8d7-2f86-4c92-a291-3fcc87e6fbf7

Hi @Mark McDonald - thanks for reporting this. Are the flow run names different even though the flow run id is the same? And can you let me know how you set the schedule? (UI or in your flow code?)

@Jenny - the flow run names are different (e.g. tomorrow's are zealous-sunfish and shaggy-bullfinch) and we set the schedules through our flow code

Thanks @Mark McDonald - Looking into this and want to make sure I understand the issue correctly. You’re seeing two flow runs scheduled at a time when you'd only expect one? And they're from different flows with the same id? Is it possible that they’re different versions of the same flow group? (Still an issue just trying to understand it.) And have you deleted any of the duplicate runs?

@Jenny - Yes, we're seeing duplicate flow runs for a single flow id (e.g. 2 flow runs scheduled for the same time). My expectation is that I would only see 1 instance of the flow run scheduled. I just looked closer at it and I see that the scheduled flow runs are different versions (zealous-sunfish is version 373 of the flow, while shaggy-bullfinch is version 375).

Thanks Mark. I think we've found the issue - normally when you register a new version of a flow the archived version’s scheduled flow runs are deleted. That hasn't happened here so you have scheduled runs for the live flow and the archived one. I don’t think re-deploying will affect anything here so feel free to do that if you need to. We’re working on a fix but I suggest you cancel any scheduled runs from the archived flow version to make sure they don't accidentally run.

thanks, Jenny