GRAX leverages a combination of asynchronous batch apex, Salesforce REST API, and the Salesforce Bulk API depending on the process. You should be aware of the execution governors and limits that Salesforce imposes in order to ensure that you can set up GRAX to work well with all the other applications you may have that are also sharing in the Salesforce resource pool.
This article is meant to provide some initial resources on Salesforce API limits. It will vary by Salesforce org, so please conduct your own analysis for your org. For more details and if you have questions on GRAX API usage for your specific org, please reach out to GRAX Support.
Asynchronous Batch Apex
One way to find out your org's limits is to use Workbench. This can be useful, for example, to see how close you are to reaching the maximum daily asynchronous apex limit.
- Log in to Workbench
- From the options presented select:
Find more general info about limits here
You can find more information regarding the Salesforce API request limits here.
You can find more information regarding the Salesforce Bulk API limits here. Note GRAX does not leverage the Bulk API 2.0.
Click here to review Salesforce's apex governor limit guide.
The maximum number of Apex batch jobs that can be run concurrently is typically 5. Your org may have non-GRAX apex jobs scheduled each day, and when you kick off any GRAX backups/archives it will create various other apex jobs. If more than 5 are trying to be run concurrently, Salesforce does have a queuing process to handle this and kick off the next in line in the queue when ready.
The maximum number of asynchronous Apex method executions (batch Apex, future methods, Queueable Apex, and scheduled Apex) per a rolling 24-hour period is typically 250,000 or the number of user licenses in your org multiplied by 200, whichever is greater.
Updated 8 months ago