-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Next Run
column name and tooltip is misleading
#31365
Comments
+1 to this. This was raised by our internal users after Airflow upgrade. The Next Run was assumed by many as the date the execution should happen though it is only data interval start and many missed the hover over part thinking it's a plain button. We modified it to show |
@wolfier @hussein-awala @bbovenzi I would like to take this up if nobody is working actively towards it. |
Looks like. Propose in PR and then it might be fine-tuned :) |
As of Airflow 2.6.3 the "Next Run" listed on the DAG page is still in the past. For example, I have a DAG that runs on the first of the month at 8PM. The next run is 2023-09-01, 20:00:00, but the DAG UI for "Next Run" show 2023-08-01, 20:00:00, which is the data_interval_start, and is in the past. Wouldn't it be more accurate for this UI component to display the data_interval_end, which is the actual datetime of the next run? It appears the commit in #31467 just changes the tooltip text, however I believe the true change needed is to change the actual UI component to use data_interval_end instead of data_interval_start for its "Next Run". Any thoughts? |
Agreed, UI is still confusing to a newcomer (speaking as a newcomer). |
Description
"Expected date/time of the next DAG Run" to me sounds like Run After.
Should the tooltip indicate something along the lines of "start interval of the next dagrun" or maybe the header Next Run is outdated? Something like "Next Data Interval"?
On the same vein, "Last Run" is equally as confusing. The header can be "Last Data Interval" in additional to a tool tip that describe it is the data interval start of the last dagrun.
Use case/motivation
Users confused "Next Run" as when the next dagrun will be queued and ran and does not interpret it as the next dagrun's data interval start.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: