apache/airflow

TriggerDagRunOperator: button Triggered DAG not shown

Open

#60,867 opened on 2026年1月21日

GitHub で見る
 (13 comments) (0 reactions) (0 assignees)Python (44,809 stars) (16,781 forks)batch import
area:Triggererarea:UIarea:coregood first issuekind:bug

説明

Apache Airflow version

3.1.6

If "Other Airflow 3 version" selected, which one?

No response

What happened?

Looks like this issue was not fixed https://github.com/apache/airflow/issues/58928 - in Airflow 3.1.6 - the behavior is the same, with a small difference - when the task has been finished - button appears without a page refresh. But when the task is running - button is unavailable.

What you think should happen instead?

The button Triggered DAG should be available right after the child DAG is started (or queued) and not when the child DAG is finished, and the browser page is refreshed.

How to reproduce

Try any DAG with TriggerDagRunOperator as an example.

Operating System

linux

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

コントリビューターガイド

技術スタック
python
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
なし
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
50
調査方針
The issue reports that the 'Triggered DAG' button is not shown while the child DAG is running, only after completion and page refresh. The previous attempt to fix this was in issue #58928, which appears incomplete. To resolve, investigate the TriggerDagRunOperator's UI component, likely in the Airflow UI codebase (e.g., `airflow/ui/`). Look for the logic that controls the visibility of the 'Triggered DAG' button based on the DAG run status. Check if the button's visibility is updated reactively when the DAG run state changes from queued to running. The fix likely involves ensuring the button appears immediately after the child DAG is triggered, without requiring a page refresh.