What Is Governor Limits in Salesforce?

Governor limits are per-transaction caps Salesforce enforces on shared resources - SOQL queries, DML rows, CPU time, heap size - so that no single tenant can

Updated 2026-09-09

Governor limits are per-transaction caps Salesforce enforces on shared resources - SOQL queries, DML rows, CPU time, heap size - so that no single tenant can degrade the platform for others.

In more detail

They are enforced at runtime and cannot be raised. Code that exceeds one fails the whole transaction with a limit exception rather than degrading.

The best-known ones are 100 SOQL queries and 150 DML statements per synchronous transaction, and 50,000 records returned per transaction.

Why it matters for admins

  • Bulk data operations that fire triggers or flows can hit them even when your own code is clean.
  • They are distinct from org limits - daily API calls, storage - which apply across the org rather than per transaction.
  • A mass update that succeeds on 200 rows can fail on 2,000 for limit reasons alone, which is why batching matters.

Frequently asked questions

Can governor limits be increased?
No. They are fixed by the platform. The response is to write bulk-safe code and batch the work, not to request an exception.
Do governor limits apply to declarative automation?
Yes. Flows and other declarative tools consume the same transaction limits as Apex, which is why complex flow chains fail on large data loads.

More from the Glossary

Related reading