Use of retired Workflows and Process Builders
Why is this an issue?
Salesforce has retired Workflow Rules and Process Builders in favor of Flow. Support and bug fixes for both ended on December 31, 2025. While existing automations continue to run, these tools:
Will not receive new features or enhancements
May face deprecation of certain capabilities
Create technical debt as they cannot be consolidated with Flow-based automation
Migrating to Flow provides a unified automation platform with better performance, more features, and ongoing support.
Examples
Process Builder - a .flow file with processType set to Workflow is flagged:
<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
<processType>Workflow</processType>
<label>Update Account Status</label>
</Flow>
Workflow Rule - any .workflow file is flagged:
<Workflow xmlns="http://soap.sforce.com/2006/04/metadata">
<rules>
<fullName>Send notification on update</fullName>
<active>true</active>
<triggerType>onCreateOrTriggeringUpdate</triggerType>
</rules>
</Workflow>
The fix for both is to recreate the automation as a Flow:
<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
<processType>AutoLaunchedFlow</processType>
<label>Update Account Status</label>
<start>
<triggerType>RecordAfterSave</triggerType>
<object>Account</object>
</start>
</Flow>
How can I fix violations?
Audit existing automation: Document what each Workflow Rule or Process Builder does.
Use the Migrate to Flow tool: Salesforce provides a "Migrate to Flow" tool in Setup that can automatically convert many Workflow Rules and Process Builders.
Manually recreate complex logic: For automations the tool cannot convert, manually recreate them as Flows.
Test thoroughly: Ensure the new Flows behave identically to the original automation.
Deactivate and delete: Once migrated and tested, deactivate and remove the old Workflow Rules and Process Builders.
See the Migrate to Flow tool considerations link in the resources section for details on what it can and cannot convert.
When should I disable this rule?
There is generally no catch-all reason to disable this rule. All Workflow Rules and Process Builders should eventually be migrated to Flow. You may dismiss specific violations temporarily while planning migration if the automation is low priority or the migration is complex.
Resources