Channels
pacc-oct-11-12-2023
pacc-july-11-12-2023
pacc-sept-20-21-2023
pacc-aug-16-2023
pacc-aug-29-30-2023
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
pacc-sept-26-27-2023
pacc-july-6-2023
intros-test
livestream-chatter
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
pacc-london-2023
pacc-sept-13-14-2023
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
pacc-july-17-18-2023
introductions
prefect-server
data-tricks-and-tips
prefect-aws
prefect-gcp
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-ui
prefect-kubernetes
pacc-aug-22-23-2023
prefect-community
Powered by
#prefect-community
Title
b
Braun Reyes
07/10/2023, 8:00 PM
Has anyone seen this behavior on local Prefect with interval schedules? this deployment cli flag set:
Copy code
--interval 600 --timezone America/Los_Angeles --anchor-date 2023-06-27T01:00:00Z
results in this schedule in UI Daily from Jun 26th, 2023 at 08
00
00 PM (America/Los_Angeles)
I would expect to see either 1am if it is assuming my local is PST or 3am if it assuming my local is CST
Post