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

"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.

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.

Voted.

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 :man_shrugging: