Multiple automation on the same object
Why is this an issue?
Having multiple automations (workflows, triggers, and flows) on the same object can lead to unpredictable behavior, maintenance challenges, and difficult-to-debug issues. When multiple automations fire on the same object:
Execution order conflicts: Workflows, triggers, and flows execute in a specific order, but having multiple can create race conditions.
Debugging complexity: Tracing which automation caused a particular change becomes difficult.
Maintenance burden: Changes to one automation may have unintended effects on others.
Governor limit risks: Multiple automations each consume resources independently, increasing the chance of hitting limits.
Examples
Example of an incorrect configuration:
Having multiple automations on the Account object:
Account.workflow- with active workflow rulesAccountTrigger.trigger- Apex triggerAccount_Update_Flow.flow- Record-triggered flow
Example of a correct configuration:
Consolidate automation logic:
Use a single Apex trigger with a handler framework, OR
Use flows exclusively for declarative automation.
Deactivate or remove redundant workflows.
How can I fix violations?
Audit all automations on the affected object (workflows, triggers, flows).
Decide on a consolidation strategy:
Apex-first: Move all logic to a trigger handler framework.
Flow-first: Migrate workflow rules to record-triggered flows.
Deactivate workflow rules that duplicate other automation logic.
Test thoroughly to ensure behavior is preserved.
When should I disable this rule?
You may want to dismiss this issue if the automations have clearly separated, non-overlapping responsibilities.
Resources