Improve Graph View Performance by bbovenzi · Pull Request #65031 · apache/airflow

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi · 2026-04-10T20:33:45Z

Make it easier to navigate by restoring "Zoom to Task" button and increase minZoom to 0.01 for large dags
Use Elk Worker to move calculation off the main thread
Reduce number of times we're walking through all Nodes and Edges
Simplify Node components by disabling unused callbacks
Simplify elk graph calculation settings for large graphs (edge thoroughness and opting for simple placement)
Turn off minimap for truly large dags (requires calculating the graph twice)

Closes#64970

Was generative AI tooling used to co-author this PR?

Yes Claude Sonnet 4.6

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

LGTM, tested, working as expected.

Just realized that the Graph isn't updated live on auto-refresh (right panel is, but we need to force a refresh to get the TI current status). That problem isn't related to this code change. Interacting with the graph to trigger a re-render will make it refresh tough

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

github-actions · 2026-04-20T12:29:39Z

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. Closes: #67714

…l nodes (apache#67720) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from apache#65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in apache#67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Closes: apache#67714

…l nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2) Closes: #67714 Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>

bbovenzi added this to the Airflow 3.2.1 milestone Apr 10, 2026

bbovenzi added area:UI Related to UI/UX. For Frontend Developers. backport-to-v3-2-test labels Apr 10, 2026

boring-cyborgBot added area:translations translation:default labels Apr 10, 2026

vatsrahul1001 modified the milestones: Airflow 3.2.1, Airflow 3.2.2 Apr 14, 2026

bbovenzi added 2 commits April 14, 2026 16:54

Add various improvements to graph view
bf6f34c

fix tests
d310600

bbovenzi force-pushed the improve-graph-performance branch from c877ef8 to d310600Compare April 14, 2026 22:00

bbovenzi marked this pull request as ready for review April 15, 2026 16:00

bbovenzi requested review from choo121600, guan404ming, pierrejeambrun, ryanahamilton, shubhamraj-git and vatsrahul1001 as code owners April 15, 2026 16:00

pierrejeambrun mentioned this pull request Apr 17, 2026
API - UI Optimization #62020
Closed

pierrejeambrun approved these changes Apr 17, 2026
View reviewed changes

pierrejeambrun merged commit f6a354d into apache:mainApr 20, 2026
401 of 403 checks passed

pierrejeambrun deleted the improve-graph-performance branch April 20, 2026 12:28

github-actionsBot pushed a commit that referenced this pull request Apr 20, 2026
[v3-2-test] Improve Graph View Performance (#65031)
8a89c8d
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

bbovenzi added a commit that referenced this pull request Apr 21, 2026
[v3-2-test] Improve Graph View Performance (#65031)
476d967
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

bbovenzi added a commit that referenced this pull request Apr 21, 2026
[v3-2-test] Improve Graph View Performance (#65031) (#65537)
5497368
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

vatsrahul1001 pushed a commit that referenced this pull request Apr 23, 2026
[v3-2-test] Improve Graph View Performance (#65031) (#65537)
6735673
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

vatsrahul1001 pushed a commit that referenced this pull request Apr 27, 2026
[v3-2-test] Improve Graph View Performance (#65031) (#65537)
d60aca1
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

vatsrahul1001 pushed a commit that referenced this pull request May 20, 2026
[v3-2-test] Improve Graph View Performance (#65031) (#65537)
cac5d9d
* Add various improvements to graph view * fix tests (cherry picked from commit f6a354d) Co-authored-by: Brent Bovenzi <brent@astronomer.io>

vatsrahul1001 mentioned this pull request May 29, 2026
UI: Fix Graph layout for TaskGroup tasks wired to external nodes #67720
Merged
1 task

github-actionsBot mentioned this pull request Jun 1, 2026
[v3-2-test] UI: Fix Graph layout for TaskGroup tasks wired to external nodes (#67720) #67830
Merged