WebUI does not show "Task Tries" items after rerun on MappedOperators

[AutomationDev85]

Apache Airflow version

2.10.1

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

No response

What happened?

We are running a Airflow 2.10.1 instance an facing the issue that the "Task Tries" fields are missing on Mapped Operator tasks:

On Normal Operators it is working fine:

Any one else has the problem? I´m not sure it was working in 2.10. or not but in 2.9.3 it was working.

What you think should happen instead?

No response

How to reproduce

Clean task state of Mapped Operator task and check the "Task Tries" items of the WebUI.

Operating System

Debian GNU/Linux 12

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

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

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

[jscheffl]

I did a regressionin breeze with DAG example_dynamic_task_mapping_with_no_taskflow_operators and can confirm:

Airflow 2.9.3:

Airflow 2.10.0:

Airflow 2.10.1:

...it seems the header "Task Tries" is added but the buttons to switch are missing. For the task details this is degrading to state of 2.9.3 but for logs this blocks UI access to logs for runs which are not the last if multiple tries :-(

...and just now the release of 2.10.2 :-( Can confirm that the bug is also in 2.10.2

[jscheffl]

With some triaging through the release notes... PR #41483 seems to be the fix that caused the side effect. Manually reverting the commit 5dcc2ad fixes this problem but re-adds the refresh issue we had in 2.10.0. ...and damn it was myself testing and did not check the mapped tasks.

@AutomationDev85 are you willing to supply a patch for the views of mapped tasks for a future 2.10.3?

[jx2lee]

Could i take this issue? if possible, please assign to me and try it!

[jscheffl]

Ah, just checked for this and was hoping it is in 2.10.3... but still not fixed :-(

[potiuk]

Ah, just checked for this and was hoping it is in 2.10.3... but still not fixed :-(

You know what's the fastest way @jscheffl 😛 ?

[jscheffl]

Ah, just checked for this and was hoping it is in 2.10.3... but still not fixed :-(

You know what's the fastest way @jscheffl 😛 ?

Yeah... the fastest way is always... fix it yourself! Probably gonna do this. I was losing track and actually we have an "everyday problem" as the UI history is broken... was just not following-up, lese I would have fixed already... but now too late for 2.10.3 :-( (Except if other major bugs will be found...)