The human-centric platform for production ML & AI

Outerbounds

Does the `@schedule` decorator take into account daylights savings when run on either AWS SFN or Argo Workflows?

the cron schedules are all in UTC, which does not have daylight savings

e.g. a cron schedule that evaluated to 4am in your respective time zone when daylight savings was on (e.g. prior to last weekend), will now be running at 3am within that same time zone

Thanks <@U0242S4KF7Y> gotta update a bunch of pipelines now :sweat_smile:

Worth noting that the `@schedule` decorator does have an optional `timezone` parameter, which is (only) supported in Argo Workflows.