Fix CLI asset materialization to use correct dag run type#63815
Merged
Conversation
pierrejeambrun
approved these changes
Mar 17, 2026
Lee-W
approved these changes
Mar 17, 2026
fat-catTW
pushed a commit
to fat-catTW/airflow
that referenced
this pull request
Mar 22, 2026
techcodie
pushed a commit
to techcodie/airflow
that referenced
this pull request
Mar 23, 2026
abhijeets25012-tech
pushed a commit
to abhijeets25012-tech/airflow
that referenced
this pull request
Apr 9, 2026
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.
Was generative AI tooling used to co-author this PR?
closes: #63809
When materializing an asset via CLI command:
airflow assets materialize, the created DAG run hadrun_type=MANUALwhich is a bug. UI did it properly and had it asASSET_MATERIALIZATION, so rectifying this behaviour in CLI to match UI.I updated
trigger_dag()helper to accept an optionalrun_typeparameter (defaulting to MANUAL for backward compatibility), allowing call sites to specify the correct run type or not for default.Run id is also updated for consistency.
Working here:

First one is after the fix, Second one before the fix (both CLI), and third one is from UI
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.