# Feature Request : Query/Agg Where Used app name

**URL:** <https://community.tulip.co/t/feature-request-query-agg-where-used-app-name/15141>\
**Category:** Product Suggestions\
**Created:** [June 26, 2025, 1:01pm UTC](https://community.tulip.co/t/feature-request-query-agg-where-used-app-name/15141 "2025-06-26T13:01:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jay.shah](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay.shah](https://community.tulip.co/u/jay.shah)\
**Post date:** [June 26, 2025, 1:01pm UTC](https://community.tulip.co/t/feature-request-query-agg-where-used-app-name/15141/1 "2025-06-26T13:01:51Z")

</div>

Hey Team,

I heavily rely on queries and aggregations across almost all of my applications. However, when there’s a business logic change or I need to fix a bug, I often have to update an existing query or aggregation.

The challenge is that I don’t have visibility into where those queries or aggs are being used across different applications. This makes it risky to make updates, as I might unintentionally break something in another workflow.

A feature that allows us to trace or view all the applications, steps, or contexts where a specific query or aggregation is used from **table** would be incredibly helpful. It would significantly reduce the risk of unintended side effects and make updates risk free and faster.

---

<div class="post-metadata">

**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\
**Post date:** [June 28, 2025, 1:10pm UTC](https://community.tulip.co/t/feature-request-query-agg-where-used-app-name/15141/2 "2025-06-28T13:10:58Z")

</div>

Hi Jay, this would fit into our longer term vision for dependency management - to have a place where you could see dependencies used in an app, and per resource.

We’re starting with Connector Functions (and eventually Functions), but the vision is to be able to see a trace for all dependencies, including Tables, Queries, Aggregations, User Groups, etc.

This is a bit of a ways out, with the initial dependency management/resource pane work for Connector Functions scheduled first. We’ll keep an eye on upvotes here for prioritization, and and also see if there’s a smaller quick win we can do to improve findability in the short term.