avanish-garg opened a new issue, #72380: URL: https://github.com/apache/airflow/issues/72380
### Problem `CronTriggerTimetable`/`MultipleCronTriggerTimetable` support `run_immediately` (run the most recent possible Dag run right away instead of waiting for the next scheduled boundary). `CronDataIntervalTimetable` and `DeltaDataIntervalTimetable` — the timetables behind the more common `schedule="@daily"` / `schedule=timedelta(...)` style, especially with `create_cron_data_intervals=True` — have no equivalent option; they always wait for the next boundary. ### Rough approach The primitives `CronTriggerTimetable` uses for this (`_calc_first_run`) are already shared with the data-interval timetables via `CronMixin`/`DeltaMixin`, so this looks like a port of an existing mechanism rather than new architecture — adding the same `run_immediately: bool | datetime.timedelta` parameter to `CronDataIntervalTimetable` / `DeltaDataIntervalTimetable`, wired through the same first-run calculation logic they already share with the trigger-style timetable. Want me to send a PR for this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
