What it requires. Record-triggered flows that only update fields on the record that triggered the flow must use Before Save context, not After Save.
Why it matters. Before Save flows update the triggering record without consuming a DML statement. Each DML statement counts against the per-transaction limit of 150. In orgs with multiple flows and triggers on the same object, unnecessary After Save DML statements accumulate quickly and can push a transaction over the limit. Before Save flows also execute faster as they avoid a separate database write.
How to fix it. Convert the flow to Before Save context. Before Save flows can directly set fields on the triggering record via Assignment elements without a separate Update Records element.
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.