# Expand “Find all uses” for columns to include server-side workflows

**URL:** <https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858>\
**Category:** Feature Requests\
**Created:** [October 12, 2025, 12:54pm UTC](https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858 "2025-10-12T12:54:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rien\_Dumore](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rien_dumore/32/79283_2.png) [@Rien\_Dumore](https://community.glideapps.com/u/Rien_Dumore)\
**Post date:** [October 12, 2025, 12:54pm UTC](https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858/1 "2025-10-12T12:54:39Z")

</div>

"Find all uses” of a column is an essential tool to safely refactor apps — but it currently ignores server-side workflows (scheduled, webhook, email, Slack, manual).

As a result, developers can unknowingly break workflows or functionality by changing or deleting a column that’s still being used there.

Proposal: Extend “Find all uses” to also scan all server-side workflows, so developers have full visibility into every dependency that references a column across the app.

---

<div class="post-metadata">

**Author:** ![NFNHello](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nfnhello/32/3371_2.png) [@NFNHello](https://community.glideapps.com/u/NFNHello)\
**Post date:** [October 12, 2025, 10:40pm UTC](https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858/2 "2025-10-12T22:40:54Z")

</div>

Yes, much needed! All this time I was thinking this behavior was a bug that never got fixed, I never thought about opening a feature request.

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [October 13, 2025, 1:19am UTC](https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858/3 "2025-10-13T01:19:43Z")

</div>

Voted.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [October 13, 2025, 2:10am UTC](https://community.glideapps.com/t/expand-find-all-uses-for-columns-to-include-server-side-workflows/84858/4 "2025-10-13T02:10:03Z")

</div>

Interestingly, it does work for some, but not all.

For example, if a column is referenced by a Query node in a Scheduled Workflow, that will show up in Find Uses. But if that same column is referenced by an Add Row node in the same Scheduled Workflow, it will not 🤷‍♂️