alexandervanloock opened a new issue, #54410: URL: https://github.com/apache/airflow/issues/54410
### Apache Airflow version 3.0.4 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? before version 3 dags where not versioned, it seems now that old tasks which were allready in the DAG are not available anymore in the main ui of the dag itself and logs are also lost <img width="389" height="109" alt="Image" src="https://github.com/user-attachments/assets/983fe827-0168-4aad-9c7f-f0a8c26153e1" /> <img width="1300" height="359" alt="Image" src="https://github.com/user-attachments/assets/a1cdf5a1-f644-4597-a9ef-5af48c04f50f" /> , it also renders the titles of the tasks weird, it is possible to find the old tasks in the task instance explorer <img width="1644" height="602" alt="Image" src="https://github.com/user-attachments/assets/68b03e10-6eb3-4537-b756-e724b64e566b" /> ### What you think should happen instead? it seems the addition of versioning messes with the history, I dont know if it is something we just have to accept or if there is a deeper underlining issue ### How to reproduce have a dag with a Taskgroup and have runs on an old version of airflow upgrade airflow to v3 and check UI ### Operating System python:3.12.0-slim-bookworm ### Versions of Apache Airflow Providers apache-airflow-providers-microsoft-azure==12.5.0 apache-airflow-providers-databricks==6.5.0 apache-airflow-providers-standard==1.4.1 ### Deployment Other ### Deployment details clean install of airflow on python:3.12.0-slim-bookworm build on a M chip mac ### 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]
