atul-astronomer opened a new issue, #63809: URL: https://github.com/apache/airflow/issues/63809
### Apache Airflow version main (development) ### If "Other Airflow 3 version" selected, which one? _No response_ ### What happened? Materialising an asset via UI creates dagrun type of `runTypes.asset_materialization` Materialising an asset via CLI creates dagrun type of `manual` <img width="1572" height="535" alt="Image" src="https://github.com/user-attachments/assets/133e83c9-9c1c-4f59-ba77-f854e5fc7cc1"; /> <img width="1537" height="475" alt="Image" src="https://github.com/user-attachments/assets/03073952-72be-4296-b76c-c38e330df2ee"; /> ### What you think should happen instead? Dagrun via both ways should be uniform. ### How to reproduce 1. Start airflow instance on main branch, make sure we have assets available. 2. Materialise an asset which has single upstream dag via UI, notice upstream dag has `runTypes.asset_materialization` type dagrun. 3. Materialise same asset now via CLI by running command `airflow assets materialize --uri <asset_uri>`, notice upstream dag has `manual` type dagrun. ### Operating System Linux ### Versions of Apache Airflow Providers _No response_ ### Deployment Other ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
