So DST caused some havoc in my flows today After the time ch

Question

So DST caused some havoc in my flows today After the time change every flow has been running two times once at it s normal time and again one hour in the future I set them using cron string in my yaml and adjusting the timezone to my local and thought based on documentation that it would auto adjust pictured So what s the plan of action here is it something I can change in the UI or do I have to re deploy all of these flows

Rich Tata · Answer

Pausing and unpausing all deployments fixed my deployment schedules for all future runs Still did anyone else encounter this issue Was this my error or a bug

Bianca Hoch · Answer

Hi Rich thank you for reaching out This appears to be a bug and we are going to file a ticket for it Can you tell us a bit more about how you applied the schedule to the flow And would you mind sharing the yaml file where you set the cron string

Rich Tata · Answer

We use CLI to create and apply deployments once the code is ready 1 prefect deployment build lt FILENAME gt py lt FLOWFUNCTIONNAME gt n lt DEPLOYMENTNAME gt q lt WORKQUEUE gt cron t lt TAG1 gt o yaml lt CHANGETHIS gt deployment yaml a We use this command template to generate a yaml cron is specified there b the Timezone is set to America Detroit in the cron file 2 prefect deployment apply yaml lt CHANGETHIS gt deployment yaml a Once we re sure it looks right we use this to deploy to prefect b verify everything is right workqueue schedule tags in the prefect UI

Rich Tata · Answer

< Bianca Hoch> Here s one of the yamls Note this issue was for every scheduled flow we have deployed across all workqueues 27 amp 7 respectively

Aaron · Answer

I had the exact same issue jobs ran twice an hour apart Mine were deployed at the command line with Python and then scheduled in the UI with cron

Bianca Hoch · Answer

Thank you for sharing this < Aaron> would you mind sharing the cron string that you set in the UI for the schedule Would you also mind providing the IDs of the affected flow runs

Bianca Hoch · Answer

< Rich Tata> Could you also provide some example IDs of the affected flow runs Thank you again

Aaron · Answer

cron string

Aaron · Answer

Flow run IDs e87d232b 990f 45a0 b4bf 71a21d5c2e8b ran at 8am 867b40a4 824a 438d b546 c5af067cc60e ran at 7am

Rich Tata · Answer

< Bianca Hoch> They were duplicates of all our flows so I don t know which were the problems and which were original I ll share a handful of pairs 78b27915 bc51 4b59 bc9c 8ff405c93973 0edb8d60 fd59 433c a995 895c4e0c3f23 19eabb57 d58f 4c4e b5af 8c790ca74f44 85c4a62b 1021 4c96 995c 98d0c4664468 5eccbbc7 dc08 4ab1 ade2 02c71bd1a203 b60d73cb 2f10 4cab 91a8 63078a0b58b7

Bianca Hoch · Answer

Thank you both Lastly would you mind sharing the versions of prefect you are using

Aaron · Answer

2 2 0

Bianca Hoch · Answer

Hey team I have created an <https github com PrefectHQ prefect issues 7461|issue here> Feel free to add to it as you see fit or request that I adjust some of the information in the details of the issue

Andrew Pruchinski · Answer

Hey < Bianca Hoch> FWIW this also happened in version 1 2 Thank you

Emil Ordoñez · Answer

Same issue here I m using schedule type Cron and Interval both of them are being repeated Common thing in all scheduled flows is an the America New York timezone We are scheduling trough the Prefect Cloud UI Prefect version on the Agent side is 2 4 0 The runs marked with an X are the ones that are repeated It s worth notice that I didn t see them coming they weren t showing as Upcoming Runs in the Flow Runs tab