What it requires. Every Decision element's default outcome must be deliberate: either connected to explicit handling, or clearly marked as an intentional no-op through a renamed outcome label or an element description. Records reaching an unconsidered default outcome pass through the flow silently.
Why it matters. Decision outcomes are evaluated top to bottom, and any record matching no outcome takes the default path. When the default outcome keeps its auto-generated label, carries no description and connects to nothing, there is no evidence the fall-through was considered. Unexpected values then pass through with no action, no error and no log, and the gap surfaces only when a business process is found to have quietly stopped working.
How to fix it. Review each Decision's default path. Where fall-through is intended, rename the default outcome to say so (for example "No action - criteria not met") or explain it in the element description. Where it is not intended, connect the default outcome to explicit handling: an error path, a logging step, or a corrective action.
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.