Fix Triggered DAG button not visible during queued/running state

[sejal-gupta-ksolves]

• closes: TriggerDagRunOperator: button Triggered DAG not shown #60867

Problem
The "Triggered DAG" button only appeared after the parent task completed execution. During RUNNING/QUEUED states, the button was completely hidden.

Root Cause:
The underlying TriggerDagRunLink reads the target redirection URL directly from XCom metadata using a specific key. By default, this XCom entry was populated downstream during the task-runner's standard finalize() routine at the very end of the task instance lifecycle.

Solution:
Modified the execution routine to eagerly calculate and push the TriggerDagRunLink URL tracking payload to XCom using context["task_instance"].xcom_push right inside the active _trigger_dag_af_3 execution block, immediately after the target run initialization occurs and before the trigger exception is raised.

This enables the FastAPI REST API /links endpoint to immediately serve the rich metadata payload, allowing the new Airflow 3 React UI to successfully render the clickable "Triggered DAG" navigation button the exact millisecond the child DAG is queued.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[jroachgolf84]

@sejal-gupta-ksolves, should we add a unit test to this? You'll also want to make suer that all checks are passing!

[potiuk]

@sejal-gupta-ksolves A few things need addressing before review — see our Pull Request quality criteria.

• ❌ Provider compat tests fail across 3 Airflow versions: Compat 3.0.6:P3.10:, Compat 3.1.8:P3.10:, Compat 3.2.1:P3.10: — 7 failing checks total. The change may rely on a symbol or behaviour not present in older supported Airflow versions. See the Checks tab.

No rush.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

---

Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting

[sejal-gupta-ksolves]

@sejal-gupta-ksolves A few things need addressing before review — see our Pull Request quality criteria.

• ❌ Provider compat tests fail across 3 Airflow versions: Compat 3.0.6:P3.10:, Compat 3.1.8:P3.10:, Compat 3.2.1:P3.10: — 7 failing checks total. The change may rely on a symbol or behaviour not present in older supported Airflow versions. See the Checks tab.

No rush.

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting

Hi @potiuk, I've updated the PR to handle this elegantly using getattr for build_airflow_dagrun_url. It also safely extracts the task instance by checking both task_instance and ti keys from the context dictionary. Clean, backwards-compatible, and all provider unit tests are passing locally.

[sejal-gupta-ksolves]

@sejal-gupta-ksolves, should we add a unit test to this? You'll also want to make suer that all checks are passing!

Hi @jroachgolf84 I have added a dedicated unit test inside providers/standard/tests/providers/standard/operators/test_trigger_dagrun.py.

[sejal-gupta-ksolves]

Hi @jroachgolf84 , just bumping this PR as it has been a couple of weeks since the requested changes were addressed.

I just rebased the branch onto the latest main. The new CI run hit some flaky external network infrastructure timeouts during the Java SDK steps—specifically, a SocketTimeoutException while trying to download the Gradle wrapper binaries (gradle-8.14-bin.zip).

Because the core logic changes for fixing the Triggered DAG button are entirely separate and passing their respective unit tests, could you please take a look when you have a moment and clear the active 'changes requested' status? Thank you!

[potiuk]

@sejal-gupta-ksolves A few things need addressing before review — see our Pull Request quality criteria.

• ❌ Build docs. See docs.
• ❌ Helm tests. See docs.
• ❌ Unit tests. See docs.

No rush.

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[pierrejeambrun]

Thanks for the pull request.

Looks like a bad rebase happened.

Many unrelated changes. Can you clean the branch please.

[jscheffl]

Cool!

Tests are added - can you re-review?