SF Profiler

Salesforce Flow limit usage analysis from debug logs

Flow automation shares transaction governor limits with Apex, triggers, workflow, and database work. SF Profiler reads Flow limit usage from Salesforce debug logs and connects that usage to the broader transaction profile.

Review Flow usage signals

When the debug log includes Flow usage events, SF Profiler can surface CPU time, SOQL queries, SOQL rows, DML statements, and DML rows for Flow interviews and elements. Those metrics make it easier to see which automation step is consuming shared limits.

Compare Flow with Apex and database work

Flow limit usage is most useful when it is not isolated from the rest of the transaction. SF Profiler keeps Flow, Apex, SOQL, DML, recursion insights, and governor limit samples in one local profile so you can compare where the budget went.

Keep investigation local

Debug logs often include record values, org details, customer identifiers, and production context. SF Profiler processes logs in the browser or desktop app, which helps troubleshoot Flow limits without sending the file to another service.