Skip to main content

Salesforce Flow Audit: Find the Flows That Overwrite Each Other

Review Flows, Process Builder, Workflow Rules, Apex triggers and validation rules on your objects. Investigate overlapping automation and plan changes in a sandbox before approval.

Last updated
By the Clientell AI teamHow we write

Which Flow, trigger or workflow rule changed that field? The audit lists every automation on an object and finds each pair that writes the same field on the same save.

Clientell AI supports org audits and drafts Salesforce metadata changes. Nothing changes in your org without your approval.

For the wider picture, run the free Salesforce health check first.

Automation Data · 2026

What patterns does the flow audit find?

Each one has a cause, a risk and a fix path.

FINDING ACritical
Per object

Opportunity object automation count

Counts Flows, Apex triggers, Workflow Rules and Validation Rules on each object, so you can see which object is overloaded.

FINDING DCritical
Trigger Order

Flows with no set run order

Record-triggered Flows on one object can run in any order unless you set one. The audit lists the Flows on each object so you can see which ones need an order.

Overlap Detector

Which automations on each object collide? Example overlap map.

Click an object to see its automation breakdown and the specific named assets that compete on save. This is sample data from a demo org.

Race detectorOn save · cross-asset
EOL flagWorkflow Rules past end of support
Sample orgDemo org
illustrative figures
Coverage Areas

What does the flow audit cover?

Six dimensions, six diagnostic surfaces, one consolidation plan.

A

Per-object automation density

Every trigger, flow, validation rule and workflow rule is counted per object. You see the full inventory for Opportunity, Lead, Account and the rest in one view.

D

Asset-level inventory

Open any object and see every named asset, such as 'Opp_AfterUpdate_Routing.flow', 'OpportunityTrigger.afterUpdate' and '2019 Stage Update WF'. Filter by type, fire condition or modified date.

E

Multi-trigger conflict surfacing

Several Apex triggers on one object are a deep source of race conditions. The audit shows the trigger order and the field-write overlap. It proposes a move to a one-trigger framework.

F

Consolidation path proposal

After reviewing the overlap, plan which automations to merge or deactivate and in what order to deploy. Clientell AI can draft metadata changes for your approval.

How risky is the number of automations on one object? Example bands

Salesforce per-object automation density thresholds and recommended action.
CountBandRiskAction
FewCleanLow. Race conditions are rare.Maintain. Annual audit.
SomeAt thresholdRace conditions appear sporadically. Coverage starts to drift.Review unsupported legacy automation and test proposed changes in a sandbox.
ManyHighRace conditions on critical fields likely. Apex test failures during deploy.Consolidation sprint this quarter.
MostCriticalRace conditions on many saves. Agentforce will not work cleanly. Production behavior is hard to predict.Pause new automation. Audit and consolidate immediately.
Warning Signs

Do any of these sound familiar?

Run the audit before the next mystery bug or failed deploy.

A

A flow change broke something nobody can explain

You updated one Flow, deployed to production, and now an unrelated field shows the wrong value some of the time. That is often a race condition. The audit lists every overlap pair so you can trace it step by step.

B

Your Opportunity object has a pile of active Flows

Every Flow, Apex trigger and workflow rule on Opportunity is one more writer on the same record save. Open Setup, then Flows, to see how many are active.

C

Old Workflow Rules are still active

Salesforce ended support for Workflow Rules and Process Builder on 31 Dec 2025. Active ones still run, and you can still edit, activate and deactivate them. If yours still fire, they can compete with the Flow that replaced them. The audit flags every one with a path to Flow. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

D

Apex test coverage just dropped after a Flow deploy

A Flow change can break a test class indirectly through trigger order. If coverage dropped, look for an overlap. Find it before the next deploy fails.

E

You are planning Agentforce on top of this org

An agent cannot work cleanly on top of competing automations. Fix the overlap first, then score your org for Agentforce.

Deliverables

What do you get with the audit?

Five deliverables, designed for admin action and architect review.

A

Automation Inventory (per object)

Every Flow, Apex trigger, Validation Rule and Workflow Rule on every object you audit. It is searchable and filterable, with last-modified dates and authors.

B

Race Condition Map

Review automations that write the same field on the same save, then agree which proposed changes to test in a sandbox.

C

Unsupported legacy automation

Unsupported since 31 Dec 2025, still running in your org. Inventory active Workflow Rules and Process Builder processes and review a migration plan with their owners.

D

Consolidation Proposal

A merged-Flow design per object, with the automation count before and after, and an impact preview for each asset.

E

Multi-Trigger Framework Migration

If an object has more than one Apex trigger, the audit proposes a one-trigger framework with handler classes and sample code.

Process Builder and Workflow Rules

How many Process Builder processes and Workflow Rules still run?

Count before you plan. Each count below uses a Setup page and a query that Salesforce documents. Run the queries with the Salesforce CLI (sf data query -o your-org -q "...") or any SOQL (Salesforce Object Query Language) tool you already use. The free audit on this page runs the same counts on every object in one scan and flags each item with a path to Flow.

Salesforce ended support for Workflow Rules and Process Builder on 31 Dec 2025, but switched nothing off. Active ones "continue to run as they did before". What stopped is customer support and bug fixes. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

Check 1

How many Process Builder processes are still active?

Setup path: Setup > Process Automation > Process Builder (or type Builder in the Quick Find box). Sort the Status column for Active.

Salesforce still lets you edit, activate and deactivate existing processes. In the API, a Process Builder process has the process type Workflow. This query counts the active ones.

SELECT COUNT()
FROM FlowDefinitionView
WHERE ProcessType = 'Workflow'
AND IsActive = true

Keep the WHERE filter. FlowDefinitionView does not support queryMore(), so a query with no filter can fail in a large org.

Sources: Workflow Rules & Process Builder End of Support (Salesforce Help); Process Builder (Salesforce Help); FlowDefinitionView object reference (Salesforce Developers).

Check 2

How many Workflow Rules do you have, and which are on?

Setup path: Setup > Process Automation > Workflow Rules (or type Workflow Rules in the Quick Find box). Sort the Active column for checkmarks.

This query lists every workflow rule and the object it runs on. The on or off flag is not a plain column, so read it from the Active column in Setup.

SELECT Id, Name, TableEnumOrId
FROM WorkflowRule

This one needs the Tooling API. With the CLI, add --use-tooling-api to the command.

Sources: Workflow Rules & Process Builder End of Support (Salesforce Help); Workflow Rules (Salesforce Help); WorkflowRule, Tooling API (Salesforce Developers).

Official Salesforce sources: Workflow Rules & Process Builder End of Support (Salesforce Help); Workflow Rules (Salesforce Help); Process Builder (Salesforce Help); Block New Workflow Rule Creation (Salesforce release note); New Process Creation Is No Longer Available (Salesforce release note); Move Processes and Workflows to Flow Builder with the Migrate to Flow Tool (Salesforce Help); Migrate to Flow Tool Considerations (Salesforce Help); Planning Your Switch to Flow Builder (Salesforce Help); Before-Save Record-Triggered Flows (Salesforce Help); FlowDefinitionView object reference (Salesforce Developers); WorkflowRule, Tooling API (Salesforce Developers).

FAQ

You have
questions,
we have
answers.

What admins and architects ask before a flow audit.

A

How do you audit Salesforce Flows?

Pull the metadata for every object (through the Metadata API or Tooling API) and list every active Flow, Apex trigger, validation rule and Workflow Rule. Then find automations that write the same field on the same save, and find Workflow Rules and Process Builder processes still active after Salesforce ended support. Check test coverage per Apex trigger and look for automations that depend on firing order. Clientell AI runs these steps for you and returns a fix plan.

B

What is a Salesforce flow audit?

It reviews Flows, Apex triggers, validation rules, Workflow Rules and Process Builder processes. Review automation overlaps and unsupported legacy automation, then test proposed changes in a sandbox. Workflow Rules and Process Builder: Unsupported since 31 Dec 2025, still running in your org.

C

How many automations should a Salesforce object have?

Salesforce sets no single limit. A safe rule: one Apex trigger per object, and no field written by more than one automation. When several automations write one field, the final value depends on which fires last. Source: Triggers and order of execution (Salesforce Developers).

D

What is a flow race condition?

Two or more automations write the same field on the same record save, and the final value depends on which one fires last. The result is a record whose value nobody can reproduce on demand. Source: Triggers and order of execution (Salesforce Developers).

E

Are Workflow Rules still supported in Salesforce?

No. Salesforce ended support for Workflow Rules and Process Builder on 31 Dec 2025. Active ones continue to run, with no customer support and no bug fixes. You can still edit, activate and deactivate existing ones, but you cannot create new ones in a normal org. The audit flags every active Workflow Rule with its Flow migration. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

F

What is the difference between a flow audit and a health check?

A health check covers all six audit dimensions: flows, permissions, data quality, technical debt, integrations and performance. A flow audit zooms into one, automation overlap. Use it when you have a specific automation problem. Use the health check for the broader picture.

G

How does Clientell AI detect race conditions?

It reads the metadata: every Flow with its target fields, every Apex trigger with its field writes (parsed from source) and every Workflow Rule with its field updates. For each object, it lists the automations that target each field. Where two or more target the same field on the same save, it flags a race condition.

H

Can I run the flow audit on a sandbox?

Yes. Start in a sandbox and review the automation inventory before proposing changes. Nothing changes in your org without your approval.

I

How is this different from Salesforce Optimizer?

Clientell AI supports org audits and a Context Graph covering Flows, Apex triggers, validation rules and permissions. Review unsupported legacy automation alongside other metadata. Confirm current Optimizer coverage with Salesforce before comparing tools.

J

Does the audit work for Process Builder processes too?

Yes. Salesforce ended support for Process Builder on the same date as Workflow Rules. The audit treats both as legacy automation with a migration path to Flow. It maps each Process Builder process to the matching record-triggered Flow. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

K

How long does consolidation take after the audit?

It depends on org size and on how many objects have race conditions. The agent drafts most of the merged Flows, and you review each one in a sandbox first.

Getting Started

Get your free
Salesforce flow audit.

Review automation overlaps and unsupported legacy automation, then plan changes in a sandbox. Run an audit during the 14-day trial, no card.

14-day free trial  ·  No credit card required

SOC 2
HIPAA
ISO 27001
Salesforce Partner