I own the flows, triggers, and rules that fire on every record change, and I treat them as production code even when they are declarative. The failure mode is a silent flow failure or a recursion loop that corrupts records for a week before anyone notices, because nothing throws an error a human sees.
Shape of it
6 indicators
Share of automation runs (flows, triggers, scheduled jobs) that complete without error.
successful runs / total runsBenchmarkPractitioner SLO 99%+; anything lower and you are corrupting records faster than you can find them
A silent automation failure leaves records half-processed while every dashboard stays green; success rate is your systems pulse.
Count of active automations (flows, triggers, workflow rules, process builders) firing on a single object.
BenchmarkPractitioner guidance: consolidate to one record-triggered flow per object per timing (before-save, after-save); 20+ overlapping automations on one object is a red flag
Stacked automations on one object create order-of-execution races and slow saves; the count is the first read on technical debt.
Share of automation logic built in declarative tools (Flow) versus Apex code.
declarative automations / total automationsBenchmarkSalesforce steers declarative-first; practitioner norm is 70-90% declarative, with Apex reserved for bulk, complex logic, or callouts
Declarative is maintainable by admins and visible in one place; every unnecessary Apex trigger raises the cost of every future change.
Time consumed processing automation on a record save, against the platform transaction limit.
BenchmarkSalesforce Apex CPU limit is 10,000 ms synchronous; practitioner target is to stay well under (e.g. below 5,000 ms) to leave headroom
Automation quietly eats the transaction budget until a big record or a bulk load blows the limit and saves start failing.
Count of failed automation runs sitting in fault logs, error queues, or paused-flow interviews.
BenchmarkPractitioner target is zero standing; alert on any growth, since a rising queue means a failure is repeating
A growing error queue is a failure that is still firing; depth over time tells you whether you are fixing or accumulating.
Frequency of automations re-triggering themselves within a single transaction (update loops).
BenchmarkPractitioner target near zero; guard with a static flag or entry criteria so a flow does not re-fire on its own field write
Recursion multiplies CPU cost and can double-write fields; it is the classic cause of intermittent, hard-to-reproduce save failures.