Flow Variables Panel: Missing Safeguards and Usage Overview for Variable Management

edwinkleinm — Mon, 31 Aug 2026 14:28:18 GMT

Context
Our company uses ServiceNow Australia.
I have been working with ServiceNow for approximately a year, during which I regularly modify existing Flows in Studio. These are often lengthy flows originally built by other colleagues, which I maintain using Workflow Studio.

One area I consistently struggle with is variable management in Flows. Each step is numbered and can reference Flow Variables, but it is not always clear whether a given variable is still actively in use. This lack of visibility makes it difficult to work confidently, especially in larger flows.

Please refer to the attached screenshots "snow_before1" and "snow_before2". In this example, the "Log" action in Step 2 is displaying "var2".

Renaming a variable does not propagate to steps that reference it. When renaming "var2" to "new2" in the Flow Variables overview, Step 2 continues to display the old name "var2", even after reopening the flow. This creates confusion.
Deleting a variable removes references silently, without any warning.
When deleting "var1" from the Flow Variables panel, ServiceNow removes its reference in Step 1 without showing a confirmation dialog or warning. This immediately results in a broken action, with no clear indication of what was affected. In some cases the flow may not break outright, but data integrity is compromised — for example, empty records being written instead of the expected value.

Feature Requests

Dead variable detection — In the Flow Variables panel, indicate which variables are no longer referenced anywhere in the flow, so they can be safely removed.
Variable usage overview — For each variable, show which step(s) it is currently being used in, providing better insight.

question Flow Variables Panel: Missing Safeguards and Usage Overview for Variable Management in Community Central forum

Flow Variables Panel: Missing Safeguards and Usage Overview for Variable Management