Open mitchnielsen opened 1 month ago
Almost a timezone issue 😂 -- you're in midwest, no?
This needs to be fixed either way, but my suspicion was that a cron string sans timezone anchors to UTC whereas the UI anchors to your local TZ. So that 5 hour difference would "make sense" if you were in EST at time of authoring.
Yup! Kansas City, set to America/Chicago
in Preferences.
a cron string sans timezone anchors to UTC
Mm, makes sense - I don't see a way at the moment to pass a timezone in flow.deploy()
, but yeah, maybe we can eventually get the UI to align them based on the timezone set in Preferences.
First check
Bug summary
The time mentioned under "Next run" doesn't match with the time mentioned under "Schedules":
This is with my timezone set to
America/Chicago
under Preferences.Reproduction
Error
Note that the "Next Run" section reports 8:00 PM, while the "Schedules" section reports 1:00 PM:
Browsers
Prefect version
No response
Additional context
Created from experience running through the Quickstart guide (https://github.com/PrefectHQ/prefect/pull/13562).
I'm still new to Prefect so it's very possible that this is either known or requires a setting I haven't set yet :)