SF Profiler

Salesforce recursion debugging for Apex and Flow

Recursive automation can hide inside long Salesforce debug logs. SF Profiler looks for repeated Apex trigger and Flow execution paths, then connects those recursion signals to the DML and automation activity that caused them.

Find repeated execution paths

The insights view highlights recursion evidence when the log shows repeated trigger or Flow paths. Instead of searching manually for recurring code units, Flow interviews, or record updates, you can review the repeated cycle and jump back to the related timeline entries.

Connect recursion to causes

Recursion usually starts with an update, insert, workflow action, Flow element, or trigger side effect that runs more automation. SF Profiler keeps causing DML entries, automation units, and related execution details together so the starting point is easier to isolate.

Understand the limit impact

Recursive paths often consume CPU time, SOQL queries, DML statements, and DML rows quickly. Because SF Profiler also tracks governor limits and Flow limit usage from the same log, you can see whether recursion is only noisy or actually pushing the transaction toward a platform limit.