Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

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.

Also, could you please move the scheduled flow output from the main slack channel to this thread to help keep the main channel tidy?

Here are the runs scheduled:

<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/5bd69e42-618e-4d62-bc72-080fd199ff1c|strange-hippo>

Scheduled

0s

Scheduled for *2022/09/01 11:31:56 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/c8b591a0-86d0-408d-8f78-c2ec9b6cd299|fanatic-swallow>

Scheduled

0s

Scheduled for *2022/09/01 11:30:56 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/a287f015-1ee9-4c78-ba31-f1f57a609e71|stirring-sparrow>

Scheduled

0s

Scheduled for *2022/09/01 11:29:56 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/da25c878-1ddc-44ab-b449-535bb96af84d|melodic-bee>

Scheduled

0s

Scheduled for *2022/09/01 11:28:56 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/9ca666b2-12d4-4295-a0cb-393a4408b9d8|literate-lemming>

Scheduled

0s

Scheduled for *2022/09/01 11:27:56 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/0718c4f5-e9a8-420f-af54-21964551889f|congenial-monkey>

Scheduled

0s

Scheduled for *2022/09/01 11:27:22 PM*
auto-scheduledIris
<http://127.0.0.1:4200/flow/d5838b37-36cb-4c87-8612-0464d3da4c10|print-pipeline-hour> / <http://127.0.0.1:4200/flow-run/b05231e2-a067-48f2-889a-58b1256b314f|opalescent-leech>

Scheduled

0s

Scheduled for *2022/09/01 11:27:17 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, <@U03ERLHR4F2>.

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.

But thanks for confirming that I am definitely doing right by investing time now in doing the update! Because initially we were planning it like next week or so

Screen Shot 2022-09-02 at 8.18.04 AM.png

<@U03V8RLCLAJ> 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.