Pranaykarvi opened a new pull request, #63962:
URL: https://github.com/apache/airflow/pull/63962

   ## Problem
   
   When a DAG uses `CronPartitionTimetable` with `catchup=False`, the scheduler 
logs a spurious error:
   ```
   dag_model.next_dagrun_create_after is None; expected datetime
   ```
   
   This happens because `next_dagrun_info()` legitimately returns `None` for 
partitioned timetables when no next run is due, but the scheduler treated 
`None` as an unexpected error condition for all timetable types.
   
   ## Fix
   
   - Changed `next_dagrun is None` check to use `not 
dag_model.timetable_partitioned` (style cleanup, same behavior)
   - Changed `next_dagrun_create_after is None` check to only log the error for 
non-partitioned timetables — partitioned timetables now skip silently since 
`None` is a valid/expected return
   
   ## Testing
   
   Added unit test 
`test_create_dag_runs_partitioned_timetable_skips_when_next_fields_none` that 
verifies a partitioned timetable DAG with both fields `None` skips without 
error logs.
   
   Fixes #63436


-- 
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]

Reply via email to