SF Profiler

Salesforce Flow debugging from transaction debug logs

Flow behavior often becomes hard to reason about once it runs alongside triggers, workflow, validation, duplicate rules, SOQL, and DML. SF Profiler reads the Salesforce debug log and keeps Flow activity connected to the rest of the transaction.

Trace automation in context

SF Profiler surfaces Flow and workflow activity on the same timeline as Apex, database calls, and limit samples. That context helps when a Flow update triggers more automation, creates repeated DML, consumes SOQL or DML limits, or contributes to CPU time.

Find recursion and repeated paths

The profiler includes insight views for repeated automation paths and recursive Flow or trigger behavior when that evidence is present in the log. This makes it easier to see which automation step started the loop and what happened afterward.

Useful when troubleshooting

• Record-triggered Flow performance issues.
• Flow updates that cause additional DML or trigger execution.
• Transactions where Flow and Apex share the same governor limits.
• Debug logs that need to stay local because they contain org or customer data.