Jacob Blanco

    Jacob Blanco

    1 year ago
    Hey folks, not sure if this is an issue with our settings but when setting a schedule in Cloud, the time is converted from UTC to our local timezone JST. So if I want the Flow to run at 11PM I have to set the schedule to run at the 14th hour. Is this expected behaviour?
    Chris White

    Chris White

    1 year ago
    Hey @Jacob Blanco - are you seeing this in the UI? This could be caused by your user preference in the UI being set to your local timezone instead of UTC (which is purely a display preference and doesn’t affect the scheduling logic). Otherwise, the only way to inform Cloud of a preferred timezone is by providing a timezone-aware
    start_time
    to your schedule / clocks - the default is UTC though
    Jacob Blanco

    Jacob Blanco

    1 year ago
    Yeah so it’s a bit confusing to be honest to set the schedule in the UI to 2PM and the Flow actually runs at 11PM. My natural expectation is that if I set the schedule in the UI to run at 2PM it will run at 2PM my time (or instance time at-least).
    I totally get that it’s complicated in case of international/remote teams, etc…. Seems like something a lot of people are gonna get bitten by. Maybe it’s worth adding UTC to the schedule card? So for the card above it would be “At 02:00PM UTC”
    Chris White

    Chris White

    1 year ago
    Ah sorry, I didn’t realize you were updating your schedule in the UI; I suspect the UI is creating schedules purely on UTC but I think this is something we could improve upon relatively easily. Would you mind opening an issue on the UI repo here: https://github.com/PrefectHQ/ui I think both the ability to specify the timezone you want for the schedule + a clearer display of the timezone being used are both valid requests here
    Thanks!