Things to Keep in Mind While Using Batch Management

How Batch Management Processes Failed Records

Batch Management doesn’t update records partially in case of any failures in the batch job. All successful record updates are committed and any changes to failed records are simply reverted back. Batch jobs without failures are marked as completed.

Batch Management Limits

You can’t do the following with Batch Management.

• Select Salesforce Shield encrypted fields in the filter criteria of a batch job.
• Create multiple versions of a batch job.
• View the details of the successfully processed records.
• Run more than five batch jobs simultaneously.
• Rerun a batch job after it’s complete.

Data and processes in your org are impacted if you delete or update a Batch Management job by updating or deleting the corresponding BatchProcessJobDefinition record. Create, update or delete a Batch Management job using the BatchProcessJobDefinition Metadata API.

CSV File Requirements for File-Based Processing

When using file-based processing, your CSV file must meet these requirements:

• Contains one column with record IDs (18-character Salesforce IDs recommended)
• Includes a header row
• Supports up to 10,000 record IDs per file
• Uses standard CSV formatting

For detailed CSV formatting guidance, see Prepare CSV Files in Bulk API 2.0 and Bulk API Developer Guide.