![]() ![]() NOTE: If the CronClock's start time is provided with a DST-observing timezone, then the clock will adjust itself. (cron, start_date=None, end_date=None, parameter_defaults=None, labels=None, day_or=None) ValueError: if provided interval is less than or equal to zero.TypeError: if start_date is not a datetime.labels (List, optional): a list of labels to apply to all flow runs generated from this Clock.parameter_defaults (dict, optional): an optional dictionary of default Parameter values if provided, these values will be passed as the Parameter values for all Flow Runs which are run on this clock's events.end_date (datetime, optional): an optional end date for the clock.start_date (datetime, optional): first date of clock.interval (timedelta): interval on which this clock occurs.Note that this behavior is different from the CronClock. This means that a daily clock that always fires at 9am will observe DST and continue to fire at 9am in the local time zone. For longer intervals, like a daily clock, the interval clock will adjust for DST boundaries so that the clock-hour remains constant. When clocks are set back, this will result in two runs that appear to both be scheduled for 1am local time, even though they are an hour apart in UTC time. For example, an hourly clock will fire every UTC hour, even across DST boundaries. Intervals greater than 24 hours will follow DST conventions, while intervals of less than 24 hours will follow UTC intervals. NOTE: If the IntervalClock start time is provided with a DST-observing timezone, then the clock will adjust itself appropriately. IntervalClocks support any interval, but if deployed to Prefect Cloud only intervals of one minute or greater are allowed. (interval, start_date=None, end_date=None, parameter_defaults=None, labels=None) Ī clock formed by adding timedelta increments to a start_date. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |