Skip to content

Airflow UI shows incorrect assets updated number after manual run #55515

Description

@karenbraganz

Apache Airflow version

3.0.6

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

No response

What happened?

Dags that are scheduled based on multiple assets might show an incorrect number of assets updated after a manual run is triggered.

I was able to reproduce this on a consumer_dag dependent on 2 assets. Before triggering a manual run, the UI shows "1 of 2 assets updated".

Image

When a manual run is triggered, the UI incorrectly displays "0 of 2 assets updated".

Image

This is incorrect because one of the assets has already been updated. As soon as the other asset is updated, a run will be triggered. Manual runs do not actually reset or delete existing asset events.

What you think should happen instead?

The "assets updated" number displayed on the UI should not change due to a manual run.

How to reproduce

  1. Create a consumer dag that is dependent on 2 assets that are updated by tasks in 2 separate producer dags.
  2. Manually trigger the producer_dag1 and notice that the UI will display 1 of 2 assets updated.
  3. Manually trigger the consumer_dag and notice that the UI will display 0 of 2 assets updated. This is incorrect. If you trigger producer_dag2 now, the dag will run because the event from producer_dag1 still counts.

I have attached example of consumer_dag, producer_dag1, and producer_dag2.

consumer_dag.py
producer_dag1.py
producer_dag2.py

Operating System

Debian GNU/Linux

Versions of Apache Airflow Providers

No response

Deployment

Astronomer

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

area:UIRelated to UI/UX. For Frontend Developers.kind:bugThis is a clearly a bug

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions