jroachgolf84 opened a new issue, #67657: URL: https://github.com/apache/airflow/issues/67657
### Under which category would you file this issue? Airflow Core ### Apache Airflow version 3.1.6 ### What happened and how to reproduce it? User note that a certain DAG picks up the outdated dag bundle even when `"run_on_latest_version": true`. At the moment the user does not have clarity on how to reproduce the initial state for it (3 out of 30 failed dags exhibited this behavior in a 24 hour period). How it manifests: 1. Task fails run on `V5` version of the dag 2. Deploy dag version `V6`, new code is visible in the Airflow UI 3. Clear task instance in Airflow UI with `Run with latest bundle version` option (confirmed by DAG audit log) 4. Airflow starts task on `V5` 5. Repeat [3] 6. Task still starts `V5` code The user then went to the DAG-level clear, picked the checkbox but *did not clear the dag run*, and the bug went away. ### What you think should happen instead? 1. Task fails run on `V5` version of the dag 2. Deploy dag version `V6`, new code is visible in the Airflow UI 3. Clear task instance in Airflow UI with `Run with latest bundle version` option (confirmed by DAG audit log) 4. Airflow starts task on `V6` ### Operating System Linux (Astronomer) ### Deployment Astronomer ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers NA ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _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]
