Override record deletion processing options for a specific table.
- # Records Per Batch : number of records to process in a single batch.
- # Records Per Batch: Max # of records to process at once.
- # Records Per Salesforce Request : maximum number of records to send to Salesforce in a single delete request. Default is 200
- # Concurrent Salesforce Requests : Max # concurrent requests to Salesforce.
Under what conditions should these options be changed?
- If timeouts occur on deletion then reducing the # Records Per Salesforce Request.
This condition can happen when it is expensive to delete a single record because of the number of
cascading deletes involved, ON DELETE triggers take a lot of time, or a record deletion workflow is costly.
- If a lot of RECORD IS LOCKED type errors are happening on a table then reducing the
@ Concurrent Salesforce Requests will often improve overall performance.
Though the application works around locked record errors automatically but retrying requests at
lower level of concurrency, there is a time cost each time a record locking error occurs.