Default logical_date to now in airflowctl dagrun trigger to match UI behavior#61047
Merged
dheerajturaga merged 2 commits intoapache:mainfrom Jan 30, 2026
Merged
Conversation
…behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience.
kalluripradeep
approved these changes
Jan 26, 2026
Contributor
kalluripradeep
left a comment
There was a problem hiding this comment.
Good improvement for CLI/UI consistency! This makes airflowctl more intuitive.
Minor suggestion:
Consider adding a test case to verify this default behavior:
def test_dagrun_trigger_defaults_logical_date():
# Test that logical_date defaults to current time when not specified
...This would prevent regression if the behaviour changes in the future.
amoghrajesh
approved these changes
Jan 29, 2026
Contributor
amoghrajesh
left a comment
There was a problem hiding this comment.
Makes sense, @bugraoz93?
bugraoz93
approved these changes
Jan 29, 2026
sanchalitorpe-source
pushed a commit
to sanchalitorpe-source/airflow
that referenced
this pull request
Jan 30, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
morelgeorge
pushed a commit
to morelgeorge/airflow
that referenced
this pull request
Feb 1, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
shashbha14
pushed a commit
to shashbha14/airflow
that referenced
this pull request
Feb 2, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
jason810496
pushed a commit
to abhijeets25012-tech/airflow
that referenced
this pull request
Feb 3, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
jhgoebbert
pushed a commit
to jhgoebbert/airflow_Owen-CH-Leung
that referenced
this pull request
Feb 8, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
25 tasks
choo121600
pushed a commit
to choo121600/airflow
that referenced
this pull request
Feb 22, 2026
…behavior (apache#61047) * Default logical_date to now in airflowctl dagrun trigger to match UI behavior When triggering DAG runs via airflowctl without specifying --logical-date, the parameter now defaults to the current timestamp instead of None. This aligns with the Airflow UI behavior where the trigger form pre-populates logical_date with the current time, providing a more intuitive user experience. * Add tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When triggering DAG runs via airflowctl without specifying --logical-date, the
parameter now defaults to the current timestamp instead of None. This aligns
with the Airflow UI behavior where the trigger form pre-populates logical_date
with the current time, providing a more intuitive user experience.