Salesforce Governor Limits are the runtime limits enforced by the Apex runtime engine to write scalable and efficient code. Such limits prevent the abuse of the resources (memory, database, processed records, and script statements) by establishing limitations.

All the applications, services, and programs run in a multi-tenant environment on the platform. There resources like memory, network, database connections are shared with every other program on the forum. Salesforce governor limits are active as Salesforce and Apex runs in a  multitenant environment. 

In this article, CloudVandana will be sharing an overview of Governor Limits in Salesforce. 

Salesforce Governor Limits

Salesforce Governor Limits are usage enforced by Salesforce to ensure efficient processing. This platform allows for multiple users of the forum without imminent performance. Salesforce governor limits depend on the Salesforce Edition. Professional Edition enables one to have 50 custom objects but 2000 for Unlimited and Performance. For example, the limit for Apex code per organization is 6MB, but this limit can be increased on a case-by-case basis by Salesforce Support. Other limits depend on the combination of Salesforce Edition and user license on the organization. 

Other governor limits are related more to programming in Apex. For example, an Apex class/ execute anon script can only have 100 select statements per transaction. Some of these limits are called ‘hard’ as they cannot be increased, so a developer’s new approach would be needed to achieve the desired result.

Types Of Salesforce Governor Limits

  1. Per-Transaction Apex Limits- Such limitations are applicable for every Apex transaction; for Batch Apex cases, boundaries are reset. 
  2. Per-Transaction Certified Managed Package Limits- If a managed package developed by a Salesforce ISV has passed security review, they are provided with generally higher per-transaction limits.
  3. Lightning Platform Apex Limit- The platform enforces these limitations as they aren’t particular to Apex transactions. 
  4. Static Apex Limits- Such limits restrict loop and apex trigger sizes, callout sizes and times, trigger code unit numbers, etc.
  5. Size-Specific Apex Limits- It regulates sizes so that no inappropriately sized items are used in the classes. 

There are other limits for non-Apex as follows-

  • Inbound Email Limits
  • Governor Limits for Salesforce API Requests
  • Push Notification Limits
  • Chatter Rest API  Limits
  • SOAP API Call Limits
  • Metadata Limits
  • API Query Cursor Limits
  • Visualforce Limits
  • SOQL and SOSL Governor Limits in Salesforce. 

Importance Of Salesforce Governor Limits

Governor limits in Salesforce prevent other organizations from using and executing lengthy code, which can take up a lot of space in the memory and even the entire cloud CPU.  As Apex provides wholly different or unique coding limits, these governor limits help the users with the proper coding with Apex. 

Are you looking for a registered Salesforce Partner for a seamless Salesforce integration and automated business process? Please feel free to contact CloudVandana today to get started. 

Request a Free Consultation