Pranaykarvi commented on issue #63436: URL: https://github.com/apache/airflow/issues/63436#issuecomment-4052927462
Looking at the `CronPartitionTimetable` implementation, the issue likely stems from `next_dagrun_info()` returning `None` when `catchup=False` and no valid next run time can be computed from the cron expression relative to the current time. The scheduler expects `dag_model.next_dagrun` to be set after calling `next_dagrun_info()`, but `CronPartitionTimetable` may not be handling the `restriction.earliest` / `restriction.latest` boundary conditions the same way `CronDataIntervalTimetable` does, resulting in `None` being returned instead of a valid `DagRunInfo`. Relevant files to investigate: - `airflow-core/src/airflow/timetables/partitioned.py` — `CronPartitionTimetable.next_dagrun_info()` - `airflow-core/src/airflow/jobs/scheduler_job_runner.py` line 2043 — where the `None` check fails -- 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]
