Salesforce Governor Limits

What are the Salesforce Governor Limits?

The Salesforce Governor Limits are used to ensure that no one acquired resources from other sources; So Force.com sets major restrictions to limit the code execution. The main aim of developing these limits is to support multi-tenant architecture, where multiple organizations and customers share the same resource. Suppose if any of this governor limit does not meet the requirement, then an error will be raised and the program will halt or terminate. Therefore salesforce governor limit plays an important role in ensuring the code is scalable and doesn't violate the rules set by Force.com. These governor limits are also known as Single transaction basis and offer a single trigger execution.

Wish to make a career in the world of salesforce? Start with HKR'S salesforce online training !

Why do we need Salesforce Governor Limits?

The following are the very important factors which will explain why are salesforce Governor Limits important;

• Governor limits are a concept that all salesforce developers (and Admins to a lesser extent), must grasp.
• These governor limits will fundamentally shape the way that you architect Salesforce solutions as well as how the code is written.
• If a salesforce Governor limit is good, the associated governor issues a runtime exception that cannot be handled. This will also help the user to translate your code breaks and won't work.
• These governor limits will restrict the users to gain requirements from other people. Salesforce. Com will make use of these governor limits as it has multiple-tenant architecture, because of this advantage every organization and user shares the same resource.
• The governor limits will assure the codes are extensible and should not violate any limits. They process a single transaction base. 

Types of Salesforce governor limits:

There are six types of Salesforce governor limits such as;

• Per-transaction Apex Limits
• Per-Transaction Certified Managed Package Limits
• Lightning Platform Apex Limits
• Static Apex Limits
• Size-specific Apex Limits
• Miscellaneous Apex Limits

Let me explain them one by one,

1.Per-transaction Apex limits:

These managed transaction packages are used to pass the AppExchange security checks for majority transaction limits. These packaged limits are developed by Salesforce ISV partners and set up the organization through AppExchange within the single namespace. With the help of these Apex limits transactions, we can access any amount of certified namespaces with the help of a single transaction. The precondition is that the number of operations that can be carried out in a single namespace which should not surpass the pre-transaction Apex limits.

The following are the important operations which can be carried by these transactions throughout the namespace. The overall limit for each namespace is 11 times.

• Effective CPU utilization
• Complete heap size management
• Numerous unique namespaces
• Best transaction implementation time.

All the above operations can be performed under the restricted transactions. When we set up the AppExchange package which is developed by an unauthorized salesforce ISV partner and the code part of this AppExchange package does not have its governor limits.

2.Static Apex Limits:

Till now we have learned what are all the restrictions will be applied to the Apex transactions. Now it's time to observe additional governor limits such as callouts, loops, queries, and records with multiple transactions. The following table will explain these governors and its limits

Description	It’s limits
The callouts governor limits are a default timeout for every transaction	10 seconds required
Callout transaction request or response maximum size	6 to 12 Megabytes
The maximum SOQL runtime prior salesforce abolished transaction	2 minutes required
The maximum amount of trigger code units and classless in the Apex implementation	5,000 transactions required
Batch size of Apex trigger	200
Batch size of For Loop condition list	200
Total number of records reverted for a batch Apex query within the Database query locator	50 million

 

3.Per transaction Apex limits:

These Apex transaction limits are very useful for counting every Apex transaction. While discussing the batch Apex, limits that are present for the execution of records batch are reactivated.

The following table explains the important transaction Apex limits and their time limits;

Description	Synchronous limits	Asynchronous limits
Total SOQL Queries Used	100	200
SOQL queries retrieved records	50,000
Issued SOSL Queries	20
Issued DML statements	150
The total amount of callouts per transaction	100
Allowed send email methods	10
Apex transaction execution time	10 minutes
Salesforce servers CPU time	10,000	60,000

4.Lightning platform Apex limits:

The following table explains the important transaction limits of the Lightning platform Apex limits. But one important thing is that here we can access Apex transaction limits.

Description	Limit
The maximum amount of asynchronous method executions within 24 hours of time	25,000 limit transactions
Parallel scheduled Apex classes	100
Queued Apex jobs or active parallel	5
The maximum amount of batches submitted	5
Parallel opened query cursors per user	15
Parallel opened query cursors per user	50

5.Size-specific Apex Limits:

In this transaction method, Apex transaction limits are designed on the basis of their sizes and this will also assure that no outsized items are present in the classes.

The following table describes the limits of the Apex size:

Description	Limit
The maximum amount of characters per class	1mn
The maximum amount of triggers per class	1 million
Apex maximum code utilization	6 MB
Limit 2 of methods size	65,535

Click here to get frequently asked Salesforce interview questions & answers

6.Miscellaneous Apex limits:

This type of Apex limits the user can't perform any transaction which will lead to stop or halt the program. Miscellaneous Apex limit means error transaction limits and this further causes the no transaction limits in Salesforce.
Here are the important Salesforce Governor limits:

• Total number of SOQL queries issued: 200
• Total number of SOQL queries issued: 20
• Total number of DML statements issued: 150
• Total number of records retrieved by SOQL queries: 50,000
• Total number of records processed as a result of DML statements: 10,000

Advantages and disadvantages of Salesforce Governor Limits:

Till now I have explained the types of Salesforce Governor Limits, now it’s time to know the advantages of Salesforce Governor Limits;

Advantages:

• Visualize data using dashboards and reports
• Deliver better programs and services
• Track consultants, their activities and contributions
• Engage and strengthen your community
• Communicate more effectively
• Raise more resources
• Replace spreadsheets and standalone databases.

Disadvantages:

Only 5 concurrent batch jobs running at a time

• It’s difficult to troubleshoot
• Execution may be delayed based on severe availability
• Future methods are not allowed
• Can’t use get content/ content as PDF methods

How to avoid governor limits:

We can avoid the governor limits using the below methods:

• Avoid DML statements and SOQL queries within the FOR Loop statements
• Make sure that Apex code manages more than one records at a time this is a mandatory requirement
• For loops, we should use collections or methods
• Streamline different triggers over the same page.

Conclusion:

In this article, I have tried my best to explain the salesforce governor limits and its importance. If you are a Salesforce developer it's always good to know how to use governor limits and its advantages. I hope this article may help a few of you to get the complete idea on Salesforce governor limits and also helps salesforce community forums.

Related Article :

• Triggers in Salesforce
• Salesforce Validation