DEV Community

Demo
Demo

Posted on • Originally published at orgdoc.dev

How to detect stale Salesforce automations before they cause problems

#salesforce #crm #admin #governance

Stale automations are the silent killers in Salesforce. I've seen them cripple enterprise orgs across healthcare, finance, and retail—causing data corruption, failed processes, and angry business users. The problem? They often run undetected until a critical report fails or a sales rep can't close a deal. Here’s how to catch them before they explode.

Why Stale Automations Creep In

Enterprise orgs evolve. Fields get renamed, objects get deprecated, and new processes replace old ones. But automation artifacts linger. In a recent healthcare client, a legacy workflow rule on the Account object still referenced a deprecated field Primary_Contact__c (renamed to Account_Person__c in a migration). It fired every time an account was edited, but since the field didn’t exist, it silently failed. The result? Missing patient contact data in a compliance report—until the audit hit.

3 Proactive Detection Tactics

Don’t wait for chaos. Audit these critical areas monthly:

  • Orphaned Processes: Check for automations tied to deleted fields or objects. Use this SOQL to find workflow rules referencing non-existent fields: 
SELECT Id, DeveloperName, CriteriaFormula FROM WorkflowRule WHERE CriteriaFormula LIKE '%Primary_Contact__c%' AND ParentId NOT IN (SELECT Id FROM CustomField WHERE DeveloperName = 'Primary_Contact__c')
Enter fullscreen mode Exit fullscreen mode

In a retail client, this query revealed 12 stale workflow rules on the Opportunity object. The field Seasonal_Promo_Code__c had been retired after a platform upgrade. The rules were still triggering, causing incorrect discount calculations.

  • Conflicting Triggers: Apex triggers often accumulate. A finance client had 3 triggers on Case for the same event (after update). One was outdated, causing a race condition that blocked case assignments. Run this to spot duplicates: 
SELECT ApexClassId, Event, OrderNumber FROM ApexTrigger WHERE Status = 'Active' GROUP BY ApexClassId, Event HAVING COUNT(*) > 1
Enter fullscreen mode Exit fullscreen mode

This exposed the conflict before it crashed their support queue during a peak sales period.

  • Disabled but Unremoved: Flows and process builders sometimes get "disabled" instead of deleted. A healthcare client had a disabled flow on Lead that still consumed API limits (1.2K calls/day) because it was embedded in a button. Use: 
SELECT Id, DeveloperName, Status FROM Flow WHERE Status = 'Disabled' AND CreatedDate < LAST_N_MONTHS:6
Enter fullscreen mode Exit fullscreen mode

They deleted it, saving $22K/year in API costs.

The Human Factor

Automations don’t age alone. Track ownership: When a business analyst leaves, their flow automations get orphaned. In a manufacturing org, a legacy approval process (owned by a departed manager) was still blocking production orders. I now enforce a quarterly "automation ownership" review in our Change Advisory Board.

Build Your Prevention Habit

Don’t let stale automations become your crisis. Integrate these checks into your monthly health audits:

  • Run the SOQL queries above for all active automations.

  • Map every automation to a business process owner (not just an admin).

  • Flag any automation older than 18 months for review.

When I first started, I’d manually check a few workflows. Now I automate the checks. Stale automations are preventable—not inevitable.

Stop chasing fires. Audit your automations before they burn your org down. Get a free, automated health scan of your org to uncover stale automations and other risks. Scan your org now at orgscanner.dev.

📚 Recommended Resource: Salesforce for Dummies — great for anyone learning Salesforce.

📚 Recommended Resource: NIST Cybersecurity Framework Guide — great for anyone security frameworks.

Need a second opinion on your Salesforce org? Request a diagnostic.

Top comments (0)