Opportunity object automation count
Counts Flows, Apex triggers, Workflow Rules and Validation Rules on each object, so you can see which object is overloaded.
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.
Acme Corp · Automation Density
5 objects scanned · 608 total automations · 6 race conditions
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.
Each one has a cause, a risk and a fix path.
Counts Flows, Apex triggers, Workflow Rules and Validation Rules on each object, so you can see which object is overloaded.
Several automations write the same field on save, so the result is not predictable. The next admin, or an AI agent, will hit it sooner or later. Source: Triggers and order of execution (Salesforce Developers).
Unsupported since 31 Dec 2025, still running in your org. Review active Workflow Rules and Process Builder processes with the owners of affected Flows. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).
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.
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.
Six dimensions, six diagnostic surfaces, one consolidation plan.
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.
Two automations that write the same field on the same record save form a race condition. The final value depends on which one fires last. The audit catches every pair. Source: Triggers and order of execution (Salesforce Developers).
Unsupported since 31 Dec 2025, still running in your org. Review Workflow Rules and Process Builder processes alongside Flows, then plan any changes in a sandbox. Source: Workflow Rules & Process Builder End of Support (Salesforce Help).
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.
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.
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.
| Count | Band | Risk | Action |
|---|---|---|---|
| Few | Clean | Low. Race conditions are rare. | Maintain. Annual audit. |
| Some | At threshold | Race conditions appear sporadically. Coverage starts to drift. | Review unsupported legacy automation and test proposed changes in a sandbox. |
| Many | High | Race conditions on critical fields likely. Apex test failures during deploy. | Consolidation sprint this quarter. |
| Most | Critical | Race conditions on many saves. Agentforce will not work cleanly. Production behavior is hard to predict. | Pause new automation. Audit and consolidate immediately. |
Run the audit before the next mystery bug or failed deploy.
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.
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.
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).
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.
An agent cannot work cleanly on top of competing automations. Fix the overlap first, then score your org for Agentforce.
Five deliverables, designed for admin action and architect review.
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.
Review automations that write the same field on the same save, then agree which proposed changes to test in a sandbox.
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.
A merged-Flow design per object, with the automation count before and after, and an impact preview for each asset.
If an object has more than one Apex trigger, the audit proposes a one-trigger framework with handler classes and sample code.
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
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
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).
What admins and architects ask before a flow audit.
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.
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.
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).
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).
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).
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.
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.
Yes. Start in a sandbox and review the automation inventory before proposing changes. Nothing changes in your org without your approval.
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.
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).
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.
Audits, playbooks and services for teams cleaning up flows or preparing for Agentforce.
A guide to trigger ordering, the metadata graph and how race conditions are found.
Read morePlaybookStep-by-step playbook for consolidating competing automations safely. With a sandbox dry-run.
Read moreChecklistA checklist of flow anti-patterns, such as Get Records inside loops.
Read moreServiceBroader audit covering flows, permissions, data, technical debt, integrations.
Read moreAuditOverlapping automation blocks AI agents. Score your org before you deploy Agentforce.
Read moreAuditSister audit for Apex coverage, governor risk, and code quality scoring.
Read moreAuditPer-user risk scoring and effective access. Pairs with the flow audit for compliance review.
Read moreProductThe agent that consolidates the flows the audit surfaces. From $249/month.
Read moreProductShip consolidated flows to production with diff preview, approval and rollback on the Platform.
Read moreTrust + security posture
Flow conflicts often correlate with low Apex test coverage. Diagnose both together.
Surface the exact deployment that introduced each race condition.
Flow errors often trace back to dirty source data. Audit both surfaces.
Automation overlap blocks AI agent deployment. Score readiness now.
Last reviewed October 2026
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