What it requires. Get Records elements must not be configured to store all fields when only specific fields are used downstream. Querying every field retrieves and holds data the flow never touches, which slows the query, inflates the flow interview, and exposes fields the automation has no need to read.
Why it matters. The flow carries data it never uses. At volume that is time and heap spent on nothing, and fields exposed to an automation with no need of them.
How to fix it. Configure the Get Records element to choose specific fields, limiting the query to the fields the flow references.
Source. Lightning Flow Scanner, get-record-all-fields
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.