Vedant-Agarwal opened a new pull request, #68461: URL: https://github.com/apache/airflow/pull/68461
The timetable howto says ``last_automated_data_interval`` is ``None`` "if this is the first time ever the Dag is being scheduled" — which is technically true but operationally misleading: the ``None`` case is only encountered when the Dag processor first parses the Dag, before any Dag run exists, and the result is stored on the Dag. Every ``next_dagrun_info`` call observable during scheduling already has the previous run's interval populated, so users watching scheduler logs after unpausing a Dag never see the ``None`` case — exactly the confusion reported in the issue. This adds a clarifying note to the howto and one sentence to the ``Timetable.next_dagrun_info`` docstring so both contract surfaces say when ``None`` actually occurs. Content follows the maintainer explanation in the issue thread. closes: #27672 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5) Generated-by: Claude Code (Fable 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
