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.