Inactive workflow rules
Why is this an issue?
Inactive workflow rules add clutter to your org's configuration. They should either be reactivated if still needed or deleted entirely. Keeping inactive rules:
Increases maintenance burden.
Causes confusion about what automation is active.
Complicates metadata deployments.
See also
WorkflowInactive— flags entire workflow files where every rule is inactive (or no rules exist). Use this rule together to detect both individual dead rules and dead workflow files.
Examples
Example of incorrect metadata (inactive workflow rule):
<Workflow>
<rules>
<fullName>Update_Account_Rating</fullName>
<active>false</active>
<criteriaItems>
<field>Account.AnnualRevenue</field>
<operation>greaterThan</operation>
<value>1000000</value>
</criteriaItems>
</rules>
</Workflow>
Example of correct approach (active or removed):
<!-- Either activate if still needed -->
<Workflow>
<rules>
<fullName>Update_Account_Rating</fullName>
<active>true</active>
<!-- ... -->
</rules>
</Workflow>
<!-- Or better: migrate to Flow and delete the workflow rule -->
How can I fix violations?
Review the rule's purpose: Determine if the workflow rule is still needed.
Reactivate if needed: If the business logic is still valid, activate the rule.
Migrate to Flow: Workflow Rules are retired; consider migrating to Flow instead of reactivating.
Delete if obsolete: Remove rules that are no longer needed.
When should I disable this rule?
There are no common scenarios where this rule needs to be disabled.
Resources