nivdror opened a new issue, #35946:
URL: https://github.com/apache/airflow/issues/35946

   ### 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](https://github.com/apache/airflow/assets/131352704/9a6a834f-ea87-49cd-9cf2-f7ec35ab1d95)
   
   
   ### 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
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to