The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Screen Shot 2022-05-17 at 11.24.20 PM.png

Screen Shot 2022-05-17 at 11.25.59 PM.png

Screen Shot 2022-05-17 at 11.26.11 PM.png

I thought the offset for a partitioned job would be taken account into the schedule (3am daily) but I see 12am daily. Is there anything else I need to set?

`prev_day_floor_schedule = build_schedule_from_partitioned_job(floor_indexing.prev_day_floor_job)`

`@daily_partitioned_config(start_date=datetime(2022, 4, 17), hour_offset=3, end_offset=1)`

Hey Liezl - `build_schedule_from_partitioned_job` has an `hour_of_day` argument: <https://docs.dagster.io/_apidocs/schedules-sensors#dagster.build_schedule_from_partitioned_job>

bit confusing, but `hour_offset` affects where the partitions split, but not the default time for when schedules run

although let me double check that that's expected, since the docs for build_schedule_from_partitioned_job do say "The schedule executes at the cadence specified by the partitioning of the given job."

(even if it is unexpected, setting `hour_of_day` should work as a workaround in the meantime though)

just landed a fix for this: <https://github.com/dagster-io/dagster/pull/7954> - thanks for the report!