Dag run_id disappears on toggling runs in ui

[NilsJPWerner]

Apache Airflow version

3.1.0

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

No response

What happened?

On selecting a dag run the dag run_id is briefly shown before getting replaced with the data interval start date. Feels like they should both be kept? Was it intentional to hide run_id in the new ui?

Screen.Recording.2025-09-29.at.3.17.12.PM.mov

What you think should happen instead?

No response

How to reproduce

Click on a different dag run.

Operating System

Debian

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

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

[tirkarthi]

When a dag run is selected run_id is the value shown till the dag run details are fetched from the backend to show run_after value. This has been the logic since Airflow 3.0.

airflow/airflow-core/src/airflow/ui/src/layouts/Details/DagBreadcrumb.tsx

Line 85 in 1f976d0

label: dagRun === undefined ? runId : <Time datetime={dagRun.run_after} />,

[NilsJPWerner]

Got it. What was the reasoning for de-emphasizing run_id?

[bbovenzi]

The thought was to find a more display friendly name for dag runs, like we have display names for tasks and dags. So the thought was to use run_after. But if users prefer the raw id, we can restore it.

[NilsJPWerner]

It would be nice to have both available. We have structured our systems to lean on run_ids pretty heavily so it's great to have that readily available.

[tirkarthi]

This was changed in #56392 . cc: @jscheffl

[jscheffl]

Yes, merged already. Whereas it was subsituting the "run after" with the "run ID" now. If this is fine we can close, else we need to find some pixels and display both (but in most cases this is the same like logicalDate or container in run_id if no specific provided)

[NilsJPWerner]

Seems solved then! Thanks @jscheffl