What it requires. Record-triggered flows must set an explicit trigger order value in the start element.
Why it matters. Where multiple flows trigger on the same object and context, execution order without explicit values falls back to creation date: invisible, undocumented, and changed by any rebuild. The Well-Architected data handling pattern is that all record-triggered flows have trigger order values populated. Salesforce recommends spacing values in tens so later flows can be inserted between existing ones.
How to fix it. Assign a trigger order value in the flow's start element, spaced in tens, and document the object's intended sequence.
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.