SF Profiler

Salesforce governor limits analysis from debug logs

Governor limits are shared by the work inside a Salesforce transaction. SF Profiler helps connect limit samples to Apex, Flow, SOQL, DML, callouts, async work, and other activity found in the debug log.

Review the limits that matter

The limits view groups samples for CPU time, heap, SOQL queries and rows, DML statements and rows, callouts, future calls, queueable jobs, publish-immediate DML, and Flow limit usage when the log includes it. That makes it easier to see whether a transaction is failing because of one expensive step or many smaller operations.

Move from symptom to source

Limit usage is most useful when it is connected to execution context. SF Profiler keeps timeline entries, summaries, database operations, and raw log details close together so you can move from a high CPU or SOQL count to the events that contributed to it.

Analyze privately

Debug logs often contain details from real orgs and transactions. SF Profiler processes the log locally in your browser or desktop app, so you can investigate governor limits without sending the file to another service.