Bulk API Limits | Bulk API Developer Guide

Bulk API use is subject to the standard API usage limits. Each HTTP request counts as one call for the purposes of calculating usage limits.

Each batch must contain exactly one CSV, XML, or JSON file containing records for a single object, or the batch is not processed and stateMessage is updated. Use the enterprise WSDL for the correct format for object records.

You can submit up to 10,000 batches per rolling 24-hour period. You can’t create batches associated with a job that is more than 24 hours old. If a batch is submitted to a closed job, the batch will not be created, however it will still count against the batch allocation as a submitted batch.

Batches and jobs that are older than seven days are removed from the queue regardless of job status. The seven days are measured from the youngest batch associated with a job, or the age of the job if there are no batches. You can’t create batches associated with a job that is more than 24 hours old.

Batches for data loads can consist of a single CSV, XML, or JSON file that is no larger than 10 MB.
A batch can contain a maximum of 10,000 records.
A batch can contain a maximum of 10,000,000 characters for all the data in a batch.
A field can contain a maximum of 32,000 characters.
A record can contain a maximum of 5,000 fields.
A record can contain a maximum of 400,000 characters for all its fields.
A batch must contain some content or an error occurs.

For binary content limits, see Binary content.

Batches are processed in chunks. The chunk size depends on the API version. In API version 20.0 and earlier, the chunk size is 100 records. In API version 21.0 and later, the chunk size is 200 records. There’s a 5-minute limit for processing each chunk. Also, if it takes longer than 10 minutes to process a whole batch, the Bulk API places the remainder of the batch back in the queue for later processing. If the Bulk API continues to exceed the 10-minute limit on subsequent attempts, the batch is placed back in the queue and reprocessed up to 10 times before the batch is permanently marked as failed.

Even if the batch failed, some records could have completed successfully. To get batch results to see which records, if any, were processed, see Get Batch Results. If you get a timeout error when processing a batch, split your batch into smaller batches, and try again.

Bulk queries have an extra 2-minute limit for processing the query, which is separate from the batch processing limit. See query Limits.

Note

The length of any file name can’t exceed 512 bytes.
A zip file can’t exceed 10 MB.
The total size of the unzipped content can’t exceed 20 MB.
A maximum of 1,000 files can be contained in a zip file. Directories don’t count toward this total.

The only valid compression value is gzip. Compression is optional, but strongly recommended. Compression doesn’t affect the character limits defined in Batch size.

Any user with correct permission can abort a job. Only the user who created a job can close it.

Only the user who created a job can close it. Any user with correct permission can abort a job.

Each job can specify one operation and one object. Batches associated with this job contain records of one object. Optionally, you can specify serial processing mode, which is used only when previously submitted asynchronous jobs have accidentally produced contention because of locks. Use only when advised by Salesforce.

You can't edit the value of an external ID field in JobInfo. When specifying an external ID, the operation must be upsert. If you try to use it with create or update, an error is generated.

Batches and jobs that are older than seven days are removed from the queue regardless of job status. The seven days are measured from the youngest batch associated with a job, or the age of the job if there are no batches. You can’t create batches associated with a job that is more than 24 hours old.

The maximum time that a job can remain open is 24 hours. The Bulk API doesn't support clients that, for example, post one batch every hour for many hours.

After a job has completed, the job status and batch result sets are available for seven days after which this data is deleted permanently.

When you submit a POST body with a change in job status, you can only specify the status field value. If operation or entity field values are specified, an error occurs.

Regardless of whether the “API Enabled” profile permission is granted, portal users (Customer Portal, Self-Service portal, and Partner Portal) can't access Bulk API.

Bulk API query has the following limitations:

Feature	Functionality
Retrieved file size	1 GB
Number of retrieved files	15 files. If the query needs to return more than 15 files, add filters to the query to return less data. Bulk batch sizes are not used for bulk queries.
Number of attempts to query	15 attempts at 10 minutes each to process the batch. There is also a 2-minute limit on the time to process the query. If more than 15 attempts are made for the query, an error message of “Tried more than fifteen times” is returned. If the query takes more than 2 minutes to process, a QUERY_TIMEOUT error is returned.
Length of time results are kept	7 days.

Bulk API query doesn’t support the following SOQL:

COUNT
ROLLUP
SUM
GROUP BY CUBE
OFFSET
Nested SOQL queries