Hi @dry-beach-38304 @red-furniture-43556 @wooden-dusk-90720 @bulky-afternoon-92433 and team. While working on the Expanded DAG Mode for the Metaflow UI (PR #180), I took a deeper dive into the  metaflow-service API to see how we could make the foreach identification even more fitting and better to what we have. I noticed that while the service already computes 

is_inside_foreach

during graph post-processing, the field wasn't actually being serialized in the DAG API response. So I raised an Issue for that and I’ve just submitted a small "enabler" fix to the service that exposes this metadata. In this PR #470 My goal was to move the "heavy lifting" of graph lineage from the browser to the backend, making the UI much lighter and more reliable when rendering those high-density task grids. Excited to see this connect the dots between the API and the new visualization.