Clarify warning for partition-driven DAGs in dags next-execution #61319
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Clarifies the warning message shown by
airflow dags next-executionwhen no nextdata interval can be determined, noting that this can also occur for
dataset- or partition-driven DAGs.
Why is this needed?
With AIP-76, partition-driven and dataset-driven DAGs may not have a
determinable next execution date. The previous message only mentioned
@onceorNoneschedules, which could be misleading.This change improves CLI clarity without altering behavior.
How was this tested?
Related issue