{"id":20333,"date":"2026-08-19T12:25:35","date_gmt":"2026-08-19T12:25:35","guid":{"rendered":"https:\/\/dianapps.com\/blog\/?p=20333"},"modified":"2026-08-19T12:25:49","modified_gmt":"2026-08-19T12:25:49","slug":"salesforce-governor-limits","status":"publish","type":"post","link":"https:\/\/dianapps.com\/blog\/salesforce-governor-limits\/","title":{"rendered":"Salesforce Governor Limits: Full Reference and How to Fix Them"},"content":{"rendered":"

Governor limits are the reason code that works perfectly in a sandbox falls over in production.<\/span><\/p>\n

The two everyone knows, 100 SOQL queries and 150 DML statements, are the easy ones. They have an obvious cause and a five-minute fix; the ones that cost real time are CPU time exceeded and heap size too large, because neither has a single offending line. They\u2019re accumulated inefficiency, and most guides don\u2019t cover them at all.<\/span><\/p>\n

This is the full reference, plus the fixes for the errors you\u2019re actually seeing.<\/span><\/p>\n

Quick Answer:<\/b> Limits are per transaction, and everything firing on that save shares them: your trigger, other triggers, Flows, validation rules, managed packages. Sync gets 100 SOQL \/ 150 DML \/ 10 seconds CPU \/ 6MB heap. Async roughly doubles CPU and heap but not SOQL rows or DML. When you genuinely can\u2019t optimise further, Batch Apex resets the limits per chunk; that\u2019s the escape hatch.<\/span><\/p><\/blockquote>\n

Why Governor Limits Exist<\/b><\/h2>\n

Salesforce Is Multi-Tenant<\/b>: Your org shares infrastructure with thousands of others on the same instance. Limits stop any one tenant from monopolising shared resources.<\/span><\/p>\n

The Practical Consequence: A governor limit exception cannot be caught and handled. When you hit one, the transaction throws a runtime exception and rolls back entirely. There\u2019s no degradation, no warning, no partial success. That\u2019s why limits shape architecture rather than sitting in a performance-tuning backlog.<\/span><\/p>\n

The Full Reference Table<\/b><\/h2>\n

\"Salesforce<\/p>\n

Table of Salesforce governor limits showing synchronous and asynchronous values for SOQL queries, records retrieved, SOSL, DML statements, records per DML, CPU time, heap size, callouts, future calls, queueable jobs, and stack depth<\/span><\/i><\/p>\n

Two things to read from that table.<\/b><\/p>\n