What it requires. Every Get Records element must be immediately followed by a Decision element that checks whether the query returned a result (IsNull or IsEmpty check on the output variable). The null or empty outcome must route to an explicit error or exit path.
Why it matters. If a Get Records element returns no results and the flow proceeds without checking, any subsequent element that references the output variable will operate on a null value. This produces silent data errors, incorrect assignments, or runtime exceptions depending on context. This is one of the most common causes of UAT-passing flows failing in production.
How to fix it. After every Get Records element, add a Decision element with an IsNull or IsEmpty check on the output variable. Route the null/empty outcome to an appropriate error or exit path.
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.