o-nikolas edited a comment on issue #19264: URL: https://github.com/apache/airflow/issues/19264#issuecomment-954280195
I see an even more odd behaviour. In the URL I see a time stamp that is definitely before the triggered dag (it is from the trigger**ing** dag), but the UI still renders all recent dags (as if the filter was not applied!). When I click on the "Update" filter button to apply the filter from the URL, I indeed no longer seen the latest triggered dag run. So I'm observing two issues: 1. The filter timestamp in the url from the triggering dag does not work at all 2. When you manually update the filter, it is as @ljades described, where you do not see the latest dag run. --- UPDATE: Actually the more I look at it, the triggered dag's "Data Interval" time matches the time in the triggerer URL. But the "UTC" time is the time the triggered dag actually started running, which is well after this time. So perhaps the filter actually works on the "Data Interval" (full disclosure, I have no idea what that is) and not the "UTC" time, which is why the URL correctly shows the current dag run. But this doesn't explain why @ljades is not seeing the correct behaviour. -- 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]
