What it requires. A procedure or model carries many inactive versions or undated drafts ahead of the active version.
Why it matters. [reasoned; live-observed 27 Aug 2026] The active version is one status flip among lookalikes: people debug the wrong version, and drafts read as deployed. In production the same state is a heavier signal than in a sandbox workshop - severity is environment-modulated by design. Two allowances: a draft ahead of the active version with a FUTURE start date is deliberate staging, not sprawl - versions carry effective-date windows for exactly that; and numbering gaps alone prove nothing, because cross-org deployments renumber versions. The signal is inactive volume plus undated drafts ahead of active.
How to fix it. Retire superseded versions; keep one active optimised version and at most one deliberate draft.
Source. Salesforce Help: Build Your Pricing Procedures (versioning semantics; mechanism reasoned)
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.