Abdel39 opened a new issue, #54229: URL: https://github.com/apache/airflow/issues/54229
### Description It would be great to have an optional toggle in Graph View to expand mapped tasks into their individual instances, so users can: See task_b[0], task_b[1], etc. rendered as separate nodes Understand the dynamic structure and how it evolved at runtime Immediately spot which mapped instances failed or succeeded Even just a “+” button to expand/collapse a node would go a long way. ### Use case/motivation When using dynamic task mapping (e.g. Task A generates N instances of Task B during a single DAG run), the Graph View collapses all mapped instances into a single stacked node for Task B. While this keeps the graph clean, it hides critical execution detail: You can’t tell how many mapped instances ran at a glance You can’t see their individual statuses (some might fail, others succeed) You lose visibility into how much fan-out actually occurred This makes it hard to reason about dynamically branching DAGs, especially ones that change run-to-run based on input size or upstream behavior. ### Related issues [Issue #48727](https://github.com/apache/airflow/issues/48727) is specifically about Task Groups, not mapped tasks, and it concerns Grid View, not Graph View Nothing else for airflow 3. ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
