Skip to content

Visible DAG RUN doesn't point to the same dag run id #35946

Closed

Description

@nivdror

Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

Hi,
I was checking out airflow 2.7.2 and I've noticed that the dag run (which is visible above the graph) doesn't corresponds with logical date being passed down to the sensor/operator nor to the dag run id visible in the details view.
It looks like the data_interval_end is what being shown.
This will cause confusion among the users!

I've noticed that manually triggered dag run behave like expected(like previous releases)

The file which I included shows the problem.

Screenshot 2023-11-28 at 9 38 57

What you think should happen instead

I think you should go back to the previous way of showing the active dag run.
Meaning that the visible dag run id will correspond with the logical date and not with data_interval_end

How to reproduce

  1. Create a dag with at least one sensor/operator
  2. let it be trigger by the scheduler
  3. View the visible run , dag run id, and the grid

Operating System

amazon-linux:2023

Versions of Apache Airflow Providers

apache-airflow-providers-cncf-kubernetes==7.6.0
apache-airflow-providers-databricks==4.5.0
apache-airflow-providers-docker==3.7.5

Deployment

Amazon (AWS) MWAA

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

Activity

  1. boring-cyborg commented on Nov 29, 2023

    @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.

  2. added
    area:UIRelated to UI/UX. For Frontend Developers.
    and removed
    needs-triagelabel for new issues that we didn't triage yet
    on Dec 2, 2023
  3. added a commit that references this issue on Apr 26, 2024
    a1a1b1d
  4. added a commit that references this issue on May 16, 2024
    4dce745
  5. added 2 commits that reference this issue on Jun 4, 2024
    fbcf2bf
  6. added a commit that references this issue on Jun 5, 2024
    9db34af
  7. added a commit that references this issue on Jul 26, 2024
    62e5e77
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions