Automation Conflict Detection

Salesforce orgs grow organically. Developers add triggers. Admins build flows. Teams migrate from Process Builder. Over time, multiple automations end up operating on the same objects and fields — and without a central view, nobody knows what is interacting with what:

• Two automations updating the same field on the same record — the last one to run silently overwrites the first
• An after-update trigger performing a data change on the same object it fires on — triggering itself again in an infinite loop
• Flows and triggers both firing on the same object — with no guaranteed execution order between them
• Active Process Builder processes still running in orgs — a retirement risk that is easy to miss without a central audit
• Manual detection requires reading every trigger body and every flow element — hours of work, with no guarantee of completeness

The system scans all active automations in the org on a weekly schedule, checks them against four conflict detection rules, and surfaces every finding as a tracked record in Salesforce — with severity, a plain English description, and a remediation recommendation.

The process runs in three stages, entirely without manual intervention:

Stage 1 — Automation Inventory Collected

The system retrieves the full list of active Apex Triggers and Flows across the org — including the objects they fire on, the events they respond to, and the fields they update. This happens automatically at the start of every scheduled scan.

Stage 2 — Four Conflict Checks Run

A detection engine evaluates the collected automation data against four independent conflict rules, covering field overwrite risk, infinite loop risk, execution order risk, and deprecation risk. Each check runs across the entire org in a single pass.

Stage 3 — Findings Saved as Conflict Records

Every detected conflict is saved to a custom Salesforce object with its severity level, the automations involved, the affected object and field, and a recommended remediation step — ready for the team to review, assign, and resolve.

The Automation Conflict Detection System is a fully native solution built on Salesforce Apex and the Tooling API. The scheduled Apex orchestration layer runs end-to-end without manual intervention — retrieving every active trigger and flow across the org, evaluating them against four independent conflict detection rules, and persisting every finding as a tracked, assignable record in Salesforce.

Each capability is delivered through Salesforce technologies as follows:

• Automation Inventory Collection: The full list of active Apex Triggers and Flows is retrieved at the start of every scheduled scan via the Tooling API and SOQL, capturing the objects they fire on, the events they respond to, and the fields they update — assembled automatically with no manual input required.
• Four-Rule Conflict Detection Engine: A deterministic Apex detection engine evaluates the collected automation data against four independent conflict rules in a single pass: same-field overwrite risk (Critical), recursive trigger risk (Critical), same-object multi-automation execution order risk (High), and deprecated Process Builder detection (High). Every check runs across the entire org inventory without any external model or API call.
• Conflict Record Persistence: Every detected conflict is saved to a dedicated Automation_Conflict__c custom object with its severity level, the automations involved, the affected object and field, a plain-English description of what the conflict is and why it matters, and a recommended remediation step — ready for the team to review, assign, and resolve like any standard work item.
• Status Tracking & Lifecycle Management: Each conflict record carries an Open / In Progress / Resolved status, a scan date, and a full history of when each conflict was first detected — making automation health auditable and reportable across the entire org without additional tooling.
• Idempotent Weekly Schedule & On-Demand Scan: The system runs on a weekly schedule by default and can be triggered on demand by an administrator at any time. Each scan fully replaces prior results, so findings always reflect the current state of the org and the tool is safe to run after any deployment to validate org state.
• Reporting & Visibility: Automation_Conflict__c records and all severity, object, field, and status fields are immediately available for Salesforce Reports, list views, and dashboards with no extra configuration — giving administrators and development teams a live, prioritised view of automation health across the org.
• Architecture Principle: Deterministic Apex and Tooling API queries guarantee accuracy and auditability for everything involving automation inventory and conflict classification; plain-English descriptions and remediation recommendations are template-assembled from structured conflict metadata rather than generative output; and the scheduled orchestration layer makes the system truly autonomous — running end-to-end on its own every week and surfacing every new conflict introduced by recent deployments, rather than waiting to be asked.

Four Conflict Detection Rules — Covering the Most Critical Risk Types

The detection engine checks every active automation against four independent rules, each targeting a distinct category of conflict risk. Findings are categorised by severity so teams can prioritise what to fix first.

• Same Field Updated Twice (Critical) — two or more automations writing to the same field on the same record; the last one silently overwrites the others
• Recursive Trigger Risk (Critical) — an after-update trigger performing a data operation on the same object it fires on, with no guard in place to prevent it re-firing
• Same Object Multi-Automation (High) — both a trigger and a flow active on the same object, with no guaranteed execution order between them
• Deprecated Process Builder (High) — active Process Builder processes still running in the org, flagged for migration before the Salesforce retirement deadline

Fully Automated Weekly Scan — No Manual Steps Required

Once deployed, the system runs on a weekly schedule without any manual trigger or intervention. Every scan is idempotent — it is safe to run multiple times, and each run replaces the previous results with the latest findings from the current state of the org.

• Scheduled weekly by default — configurable to run more frequently if needed
• Can also be triggered on demand at any time by an administrator
• Each scan replaces previous results — findings always reflect the current org state
• Runs silently in the background with no impact on org performance or end users

Conflict Records in Salesforce — Tracked, Assignable, and Reportable

Every detected conflict is saved as a record in a dedicated Salesforce custom object. Each record captures the full context of the conflict — the automations involved, the affected object and field, the severity level, and a recommended remediation step — making findings trackable and assignable like any other work item.

• Conflict type and severity level recorded for every finding
• Object name, field name, and list of involved automations captured per record
• Plain English description explains what the conflict is and why it matters
• Remediation recommendation included with every conflict record
• Status tracking: Open, In Progress, or Resolved — manage fixes like any other task
• Scan date recorded on every record — full history of when each conflict was first detected

Fully Native Salesforce — No External Tools Required

The entire solution runs within the Salesforce platform using standard development infrastructure. There is no external scanning tool, no third-party integration, and no additional licence required. Conflict records, status tracking, and history all live in Salesforce alongside the automations being monitored.

• Runs entirely within Salesforce — no external application or middleware
• Works on standard Salesforce licensing
• Conflict records managed and tracked within the platform your teams already use
• Detection rules extensible by developers — new conflict types can be added without changing the core pipeline

For Salesforce Administrators

• Know exactly which automations are conflicting — before a user reports unexpected behaviour
• Deprecated Process Builder processes surfaced automatically — no manual audit needed
• Conflict records give you a clear, prioritised list of what to fix and in what order
• Weekly scan means new conflicts introduced by recent deployments are caught quickly

For Development & Release Teams

• Field overwrite and recursive loop risks detected before they reach production
• Every conflict record includes the automations involved — no manual cross-referencing required
• Remediation recommendations give developers a clear starting point for each fix
• Idempotent scanning means the tool can be run safely after any deployment to validate the org state

For Business & Operations Leaders

• Reduce the risk of silent data quality issues caused by automation conflicts overwriting field values
• Prevent production incidents from recursive triggers before they impact end users
• Maintain a live, auditable record of automation health across the entire org
• Lower the cost and complexity of Salesforce maintenance as the org scales and automation grows