pierrejeambrun opened a new pull request, #71441: URL: https://github.com/apache/airflow/pull/71441
Fixes the misleading "Triggered Dag Run" attribution in the Asset Events view. An asset event is linked to every dag run that consumed it, so when a run consumed several events the UI showed "Triggered Dag Run" on each of them — making it look as though more runs had been created than actually were. Now only a run's most recent consumed event is labelled "Triggered Dag Run"; the earlier consumed events are labelled "Included in Dag Run". The `/assets/events` endpoint flags the triggering event per run (ranking each run's consumed events by timestamp) and exposes it as a `triggering` field on `DagRunAssetReference`; the Asset Events UI renders the "triggered" and "included" groups accordingly. Scope: this covers the attribution/labelling half of the issue. The separate "older events silently ignored" scheduling behaviour was addressed by #62501 and is out of scope here. closes: #56749 ##### Screenshots (Asset Events view) — _to attach_ - Before: several events under one run each showing "Triggered Dag Run" - After: newest event "Triggered Dag Run", earlier ones "Included in Dag Run" --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
