o-nikolas edited a comment on issue #19264: URL: https://github.com/apache/airflow/issues/19264#issuecomment-954321045
> I dug through history and it seems like `TriggerDagRunOperator`'s extra link is simply out of date. Yupp that's what I saw as well. I'll patch it up so the right arg is passed in. As for the wrong date being used: after a bit more investigation, it's going to be quite tricky to get the execution date of the **triggered** dag at the point the extra link code is being evaluated. Because both the **triggered** dag's execution time and dag run id are both calculated at runtime in the `execute` method of the operator. So the webserver does not have access to the results of those computations when it's building the link. A DB query could be used to get the correct time perhaps? Not sure if it's worth doing a query each time the link is built for such a feature though (or if it's even possible because you'd need the dag run id for the query). Perhaps just linking to the dag at the current time will suffice. Thoughts? -- 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]
