Bulk API 2.0 and Bulk API Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Limits
Considering Limits
Limits are in place to ensure optimal performance for all customers and to provide fair access to system resources. Each org is only able to handle a certain number of API requests within a 24-hour period. Budget your overall API consumption to account for what each integration does against the org.
Questions that might help to plan for limits:
- How many other integrations are making API requests into your org?
- How close does your org come to reaching its entitled request limit each day?
- How many API requests per day would be required in order to address your use cases and data volume?
- Of the APIs that could do the job you’re planning, what are their limits characteristics?
So consider both what your new implementation is attempting to do as well as what existing integrations are doing to make sure your workloads won’t be interrupted.
- Batch allocations
- General limits
- Ingest limits
- Query limits
Per-Transaction Apex Limits
For Bulk API and Bulk API 2.0 transactions, the effective limit is the higher of the synchronous and asynchronous limits. Limits are detailed in Per-Transaction Apex Limits in Apex Developer Guide. For example, the maximum number of Bulk Apex jobs added to the queue with System.enqueueJob is the synchronous limit (50), which is higher than the asynchronous limit (1).
Maximum CPU Time Limit
Bulk API and Bulk API 2.0 processes consume a unique governor limit for CPU time on Salesforce Servers, isolated from the generic per-transaction Apex limit for maximum CPU time.
| Description | Value |
|---|---|
| Maximum CPU time on the Salesforce servers for Bulk API and Bulk API 2.0 | 60,000 milliseconds |