What it requires. Flow API names must follow the convention: [Domain]_[TypeCode]_[Action]. Domain is typically the primary object. TypeCode must be one of: SCR, SFL, SCH, BeforeSave, AfterSave, BeforeCreate, AfterCreate, BeforeUpdate, AfterUpdate, BeforeDelete, AfterDelete, EVT, EML.
Why it matters. A consistent naming convention allows any team member to understand a flow's type, trigger context, and purpose from its name alone, without opening it.
How to fix it. Rename the flow to follow [Domain]_[TypeCode]_[Action] convention. Refer to the SFXD Flow Naming Conventions guide for the full type code list.
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.