Select version when re-running a dag/task

[RNHTTR]

Apache Airflow version

3.0.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

When testing new dags, especially long-running dags, it's really frustrating to have to re-run a long dag just to be able to re-run the last task (e.g. there was a bug in the last task). Dag versioning is great, but it undermines the concept of task atomicity because in order to re-run a single task, I potentially need to re-run an entire otherwise perfectly functioning dag.

What you think should happen instead?

Users should be able to select a dag version when clearing a task if that task existed in previous versions.

How to reproduce

Create a dag run with a bug in the last task. Fix the bug, then clear the last task instance.

Operating System

n/a

Versions of Apache Airflow Providers

No response

Deployment

Astronomer

Deployment details

No response

Anything else?

This is arguably a feature request, but I'm considering it a bug since this functionality exists in Airflow 2.x

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[AshutoshSrivastavaDev]

Can i work on this?

[AshutoshSrivastavaDev]

@potiuk thank you so much for assigning me the ticket, will share the pr soon.

[jroachgolf84]

Just to clarify, is this because when you fix the bug in the last task, it creates a new DAG version? And trying to re-run that Task (using the existing DAG run) would use the older version?

[RNHTTR]

Just to clarify, is this because when you fix the bug in the last task, it creates a new DAG version? And trying to re-run that Task (using the existing DAG run) would use the older version?

Correct.