Backfill "Run Backwards" Option Has No Effect

[natesinger]

Apache Airflow version

3.0.0

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

No response

What happened?

It seems that when you start a backfill, the run backwards option has no effect. It will always run earliest to latest regardless of the selecting.

What you think should happen instead?

When you run backwards it should run latest to earliest instead of earliest to latest.

How to reproduce

Try to run a backfill on any DAG and observe that the "Run Backwards" option has no effect.

Operating System

Airflow 3.0.1 running on a k8s single amd64 node, but also the same on k8s arm64 with multiple nodes.

Versions of Apache Airflow Providers

airflow@airflow-api-server-867d8f7848-vjvqk:/opt/airflow$ pip freeze | grep apache-airflow-providers
apache-airflow-providers-amazon==9.7.0
apache-airflow-providers-celery==3.10.6
apache-airflow-providers-cncf-kubernetes==10.4.3
apache-airflow-providers-common-compat==1.6.1
apache-airflow-providers-common-io==1.5.4
apache-airflow-providers-common-messaging==1.0.1
apache-airflow-providers-common-sql==1.27.0
apache-airflow-providers-docker==4.3.1
apache-airflow-providers-elasticsearch==6.2.2
apache-airflow-providers-fab==2.0.2
apache-airflow-providers-ftp==3.12.3
apache-airflow-providers-git==0.0.2
apache-airflow-providers-google==15.1.0
apache-airflow-providers-grpc==3.7.3
apache-airflow-providers-hashicorp==4.1.1
apache-airflow-providers-http==5.2.2
apache-airflow-providers-microsoft-azure==12.3.1
apache-airflow-providers-mysql==6.2.2
apache-airflow-providers-odbc==4.9.2
apache-airflow-providers-openlineage==2.2.0
apache-airflow-providers-postgres==6.1.3
apache-airflow-providers-redis==4.0.2
apache-airflow-providers-sendgrid==4.0.1
apache-airflow-providers-sftp==5.2.1
apache-airflow-providers-slack==9.0.5
apache-airflow-providers-smtp==2.0.3
apache-airflow-providers-snowflake==6.3.0
apache-airflow-providers-ssh==4.0.1
apache-airflow-providers-standard==1.1.0

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

Thanks!

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

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[eladkal]

Somewhat related to #49508
cc @uranusjr @kaxil

[uranusjr]

I don’t think this should be included as a part of #49508. This is multiple runs on the same dag, and a totally different situation.

@dstandish How is this currently implemented?

[tirkarthi]

@natesinger Is this from UI? run_backwards was always false in the frontend request payload irrespective of the form value. It was fixed in 34009c5 and backported in #52168 for 3.0.3 release.

[natesinger]

@tirkarthi Yes this was in the webapp. Thanks for taking care of this!