travis-cook-sfdc opened a new issue, #32750: URL: https://github.com/apache/airflow/issues/32750
### Apache Airflow version 2.6.3 ### What happened If you go to `/dagruns/list` and choose to delete a DAGRun, it'll end up deleting all the task instances from all other DAGs with the same run_id. This bug was introduced in 2.6.0 by [#30330](https://github.com/apache/airflow/pull/30330) because it's now deleting task instances based on the `run_id`. because the `run_id` doesn't include the DAG ID in it, this delete is overinclusive. ### What you think should happen instead Only delete the task instances for the dag that's being deleted. ### How to reproduce 1. Create 2 DAGs, `foo` and `bar`. 2. Run them both for the same day so they get the `run_id` 3. Navigate to `/dagruns/list` in the webserver 4. Delete the run associated with `foo` 5. Navigate to `bar`'s grid view and see all of the task instances are gone for the day that was deleted from `foo`. ### Operating System Debian GNU/Linux 10 (buster) ### Versions of Apache Airflow Providers N/A ### Deployment Other Docker-based deployment ### Deployment details N/A ### 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]
