Salesforce Governor Limits
Since Apex runs in a multitenant environment, the Apex run time engine strictly enforces a number of limits to ensure that runaway Apex does not monopolize shared resources. These limits, or governors, track and enforce the statistics outlined in the following table. If some Apex code ever exceeds a limit, the associated governor issues a run time exception that cannot be handled.
Description
|
Limit
|
Total number of SOQL queries issued
| |
Total number of SOQL queries issued for Batch Apex and future methods
| |
Total number of records retrieved by SOQL queries
| |
Total number of records retrieved by Database.getQueryLocator
| |
Total number of SOSL queries issued
| |
Total number of records retrieved by a single SOSL query
| |
Total number of DML statements issued
| |
Total number of records processed as a result of DML statements,Approval.process, or database.emptyRecycleBin
| |
Total number of executed code statements
| |
Total number of executed code statements for Batch Apex and future methods
| |
Total heap size
| |
Total heap size for Batch Apex and future methods
| |
Total stack depth for any Apex invocation that recursively fires triggers due toinsert, update, or delete statements
|
16
|
For loop list batch size
| |
Total number of callouts (HTTP requests or Web services calls) in a request
| |
Maximum timeout for all callouts (HTTP requests or Web services calls) in a request
| |
Default timeout of callouts (HTTP requests or Web services calls) in a request
| |
Total number of methods with the future annotation allowed per Apex invocation
| |
Maximum size of callout request or response (HTTP request or Web services call)
| |
Total number of sendEmail methods allowed
| |
Total number of describes allowed
| |
Total number of classes that can be scheduled concurrently
|
25
|
Total number of test classes that can be queued per a 24–hour period
|
Visualforce Limits
Available in: Contact Manager, Group, Professional, Enterprise,Performance, Unlimited, and Developer EditionsLimit | Value |
Maximum response size for a Visualforce page | Less than 15 MB |
Maximum view state size in a Visualforce page | 135KB |
Maximum size of a Visualforce email template | 1 MB |
Maximum file size for a file uploaded using a Visualforcepage | 10 MB |
Maximum size of HTML response before rendering, whenVisualforce page is rendered as PDF | Less than 15 MB |
Maximum PDF file size for a Visualforce page rendered as a PDF | 60 MB |
Maximum total size of all images included in a Visualforcepage rendered as a PDF | 30 MB |
Maximum response size of a JavaScript remote call | 15 MB |
Default timeout for a JavaScript remoting call | 30000milliseconds (30seconds) |
Maximum timeout for a JavaScript remoting call | 120000milliseconds (120seconds) |
Maximum number of rows retrieved by queries for a singleVisualforce page request | 50,000 |
Maximum number of rows retrieved by queries for a singleVisualforce page request in read-only mode | 1 million |
Maximum number of collection items that can be iterated in an iteration component such as <apex:pageBlockTable> and<apex:repeat> | 1,000 |
Maximum number of collection items that can be iterated in an iteration component such as <apex:pageBlockTable> and<apex:repeat> in read-only mode | 10,000 |
Maximum number of field sets that can be displayed on a single Visualforce page. | 50 |
Maximum number of records that can be handled by StandardSetController | 10,000 |
SOQL and SOSL Limits
Metadata Limits
The following are limits for deploying and retrieving metadata. These limits apply to the Force.com IDE, the Force.com Migration Tool, and the Metadata API.
Metadata Limit
|
Limit Description
|
Retrieving and deploying metadata
|
Metadata API can deploy and retrieve up to 5,000 filesor 400 MB at one time.
While a specific file size limit is not enforced, you might encounter out-of-memory errors for very large files.
|
Change sets
|
Inbound and outbound change sets can have up to5,000 files of metadata.
|