Does anyone know of a bug where even though the frequency of the schedule is once in an hour, multiple runs are created for that hour? The flows keep increasing every minute. I now have 5 runs for the same hour! Here is my deployment code:

deployment = Deployment.build_from_flow(flow=print_pipeline_hour,\
                                        name="Hourly Pipeline Deployment", version="1", tags=["Iris"],\
                                        schedule={'rrule': 'FREQ=HOURLY;UNTIL=20220912T040000Z', 'timezone': "Asia/Kolkata"},
                                        work_queue_name="hour-work-queue")

Strange. If you delete that deployment and create it again from the file so you get five runs one minute apart again? If so, I would open a big report issue at prefect/prefecthq.

Here are the runs scheduled: print-pipeline-hour / strange-hippo Scheduled 0s Scheduled for 2022/09/01 113156 PM auto-scheduledIris print-pipeline-hour / fanatic-swallow Scheduled 0s Scheduled for 2022/09/01 113056 PM auto-scheduledIris print-pipeline-hour / stirring-sparrow Scheduled 0s Scheduled for 2022/09/01 112956 PM auto-scheduledIris print-pipeline-hour / melodic-bee Scheduled 0s Scheduled for 2022/09/01 112856 PM auto-scheduledIris print-pipeline-hour / literate-lemming Scheduled 0s Scheduled for 2022/09/01 112756 PM auto-scheduledIris print-pipeline-hour / congenial-monkey Scheduled 0s Scheduled for 2022/09/01 112722 PM auto-scheduledIris print-pipeline-hour / opalescent-leech Scheduled 0s Scheduled for 2022/09/01 112717 PM

This somehow seems similar to something I am experiencing currently and trying to debug and scavenger hunt for similar issues. What version of prefect are you using? I am using 2.0.4

I suggest upgrading to 2.3.1 if possible, @Michiel Verburg.

I am indeed currently in that process, after thorough debugging it seemed to indeed have to do with the whole transition from beta to GA and changes surrounding it.

@Venkat Ramakrishnan I just ran your deployment code with 2.3.1 and it created a schedule for every hour.

Not sure. I didn't find the issue consistently reproducible, so I cannot say for sure if it has been fixed in the latest version. By the way, I had been running in Windows, but now planning to shift to Linux tomorrow. If I see it again, I will update the thread. Thanks.