karenbraganz commented on issue #41406:
URL: https://github.com/apache/airflow/issues/41406#issuecomment-2316316501
Hem and I tested this out in Airflow 2.10 (Astro runtime 12.0.0) and noticed
that this bug still exists but only for certain types of runs (when the run_id
timestamp is not at the 0th second of the minute).
- When testing this out with runs scheduled to run every minute, I did not
see this bug. I was able to go to Browse -> DAG Runs, find a DAG run older than
the 25th record, click on the run ID, and open the correct DAG run page.
- However, when testing this out with manual runs, the bug became apparent.
For example, I triggered a manual run with
`run_id=manual__2024-08-28T13:54:14.979062+00:00`.
- After over 25 runs, I tried opening this DAG run by clicking on the
run_id in Browse-> DAG Runs. This opened the DAG without a specific run
highlighted (see below).
- When I clicked on a task in the graph view, it highlighted the run that
had occurred just before the run I had clicked on in the grid. The `run_id` for
this was `scheduled__2024-08-28T13:54:00+00:00` as indicated in the screenshot
below. The run I wanted to open was not part of the grid. Hem observed this as
well in his tests.
- In contrast, when I opened the DAG run for
`run_id=scheduled__2024-08-28T13:54:00+00:00`, it opened and highlighted the
correct DAG run. This might suggest that the bug only appears for manual runs,
but this is not true as described in the next bullet point.
- When I modified the DAG to have `schedule=@continuous`, the bug appeared
once again for scheduled runs indicating that it is not exclusive to manual
runs. For example, when I clicked on a run_id which was
`scheduled__2024-08-28T16:47:22.632138+00:00`, I saw the same bug as before
where it opened a page without any DAG run highlighted. When i clicked on one
of the tasks in the graph, it highlighted the run previous to what I clicked on
in the grid. The `run_id` for this was
`scheduled__2024-08-28T16:47:20.415112+00:00`, and the run I was looking for
was not visible in the grid. Hem observed this as well in his tests.
- Based on these observations, I believe the bug appears only for DAGs with
run ID timestamps that are not at the 0th second of the minute. Due to the bug,
you are only able to see the run previous to the run you wanted to locate. It
does not depend on whether the run was scheduled or manually triggered. For
example, the bug appeared for
`run_id=scheduled__2024-08-28T16:47:22.632138+00:00` but not for
`run_id=scheduled__2024-08-28T13:54:00+00:00`.
--
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]
