How to dynamically set run_config each time a schedule runs?

[dagsir[bot]]

Hello! 👋 I’m not sure what I have is a bug or intended behaviour - I’m trying to configure a schedule with a variable argument to the run config that should be calculated when the schedule launches a run. Something like this:

my_schedule = ScheduleDefinition(..., run_config={... "time": datetime.now(timezone.utc).strftime("%Y-%m-%d 00:00:00")})
When I try this locally, everything is fine, with the run config changing dependent on the current date.

However, for the scheduled executions it seems that datetime.now is computed on deployment and is then left static; it has supplied the same run config for the last 3 days, all referring to the date of the last deploy before the weekend.

Is this expected? Should I be supplying a variable run config some other way? Or is this indeed a bug that I should raise a ticket for?

Thanks! 🙏

---

The question was originally asked in Dagster Slack.

[smackesey]

You can use run_config_fn on ScheduleDefinition: https://docs.dagster.io/_apidocs/schedules-sensors#dagster.ScheduleDefinition

Or you can just use a custom eval function that sets run_config on RunRequest. See the schedule docs: https://docs.dagster.io/concepts/partitions-schedules-sensors/schedules