Salesforce Org Limits: Governor Limits in Salesforce

Jessica B.

Seasoned technical writer giving you top Salesforce Tips.

Updated: Jan 13th, 2025

Salesforce Limits

Salesforce imposes a variety of limits to ensure fair use of its resources. The limits you can use will depend on your specific Salesforce edition and the platform you are using.

Common Limits

API Limits – These limit the number of API requests you make to interact with Salesforce.

Salesforce Mass Email Limits – Controls the number of emails you can send out through Salesforce and includes single email and mass email communications.

Apex Limits – Controls limits on DML operations, limits of CPU, and heap size for Apex code execution.

Governor Limits – Set limits to ensure fair use of the Salesforce system.

Salesforce DML Limits – Controls the number of database operations you can perform in one transaction.

Lightning Component Limits – Restricts the number of Lightning components and the amount of client-side storage you can utilize.

Report and Dashboard Limits – Controls the amount of dashboards, reports, and report results you can generate and store.

Streaming API Limits – This Streaming API limit includes the number of client connections and events per hour.

Custom Metadata Limits – This limits how many custom metadata records you can create within your Salesforce org.

Workflow Limits – Limits the number of workflow rules, automation elements, and field updates you have in your Salesforce org.

SOQL and SOSL Limits – Salesforce Object Query Language (SOQL) and Salesforce Object Search Language (SOSL) are two sets of query languages used in Salesforce for searching data, each one will have limits on the search queries.

These are just a few common limits that you should be aware of when designing and developing using the Salesforce platform to ensure your applications, automation, and processes are efficient within the various limits and constraints.

Governor Limits in Salesforce

Salesforce governor limits are runtime constraints and limits imposed on executing code to ensure efficient and fair use of the system resources. By implementing limits you can mitigate the degradation of the Salesforce platform by preventing resource-intensive operations. If a governor limit is surpassed or violated, the process will be paused and Salesforce will display an error.

These limits are crucial when it comes to developing your applications on the Salesforce platform. Your code should be optimized and efficient to ensure processes work within these limits. If you need to work with large sets of data regularly then your code will need to be designed accordingly and potentially implement asynchronous processing methods to prevent exceeding these limits.

Salesforce Apex Limits

Apex is Salesforce’s programming language and runs in a multitenant environment. The runtime engine enforces limits on any runway Apex code or processes to ensure they won’t monopolize shared resources.

Salesforce Transaction Limits in Apex

For each Apex transaction, these limits count. When it comes to Batch Apex, the limits are reset for each execution of a batch of records in the execute method.

Per-Transaction Certified Managed Package Limits

Certified managed packages have passed a security review for the AppWExhange and have their own set of limits for the most per-transaction limits.

Lightning Platform Apex Limits

Restricts the number of Lightning components and the amount of client-side storage you can utilize.

Static Apex Limits

These limits apply to the default timeout of callouts in a transaction, maximum size of callout request or response, maximum SOQL query run time before Salesforce cancels the transaction, maximum number of class and trigger code units in a deployment of Apex, Apex trigger batch size, For loop list batch size and maximum number of records returned for a Batch Apex in query in Database.QueryLocator.

Size-Specific Apex Limits

These limits apply to the maximum number of characters for a class, the maximum number of characters for a trigger, maximum amount of code used by all Apex code in an org, and the method size limit.

Miscellaneous Apex Limits

These include; Connect in Apex, Data.com and Clean, Event Reports, SOQL Query Performance, and MAX_DML_ROWS limit in Apex testing.

Salesforce API Limits

API Limits and allocation are applied to Salesforce Platform SOAP and REST APIs and other APIs built on those frameworks. There are three types of limits imposed; Concurrent API Request Limits, Salesforce API Timeout Limits, and Total API Request Allocations. These API limits in Salesforce are used to maintain optimum performance.

Org Limits Salesforce: Concurrent API Request Limits

There are concurrent API limits Salesforce for various types of Salesforce orgs for concurrent inbound requests (known as calls) with a duration of 20 seconds (or longer).

Developer Edition and Trial orgs – Limit of 5

Production orgs and Sandboxes – Limit of 25

If the limit is exceeded, the API will return an exception code. Any new concurrent requests will not be processed until there are fewer requests than the allowed limit. Note that there is no limit on the number of concurrent requests if they are shorter than 20 seconds.

Salesforce API Timeout Limits

The timeout limit is 10 minutes for REST and SOAP API calls. The timeout is set by SOQL limits. We recommend reading here for a breakdown of the specific limits.

If a request reaches a limit, the API will return a request running too long error for SOAP APIs and a query timeout exception code for the REST API.

Salesforce Inbound API Call Limit

There are limits for the total inbound API requests per a 24-hour period per Salesforce org.

It’s important that you monitor your API usage and keep the limits in mind. You can always set up your Salesforce org to send an email to a specific user if the number of API requests exceeds a specific percentage of your allotted amount.

Salesforce Email Limits

Each licensed Salesforce org can send a single email to a maximum of 5,000 external email addresses per day based on GMT. If you send single emails using the email author or composer in Salesforce, it won’t count towards this limit. There isn’t any kind of limit when sending single emails to leads, contacts, person accounts, and users in your org differently from the Account, Contact, Lead, Opportunity, Campaign, Case, or custom object pages.

In Lightning Experience, any email sent via an approval process instead of directly from the email composer will count towards the limit.

We hope to see you soon! 

• Twitter
• Facebook
• YouTube
• LinkedIn

Disclaimer: The comparisons listed in this article are based on information provided by the companies online and online reviews from users. If you found a mistake, please contact us.