You cannot configure the chunk size in either Bulk API version. Unless you're using API 20 or before (which definitely should not be an option), chunks will be 200 records in size. You can configure the batch size, but that's more about managing the Bulk API's limits on the byte size of a batch than anything else, and doesn't alter the chunk size. Because ...
Did you create the batch and pass the batch size in your code ? If you are calling the code from batch class :
BatchCLass bc= new BatchCLass();
This will process only 50 records at a time..
Can you share a snippet you are using for better response if this does not work for you?
What you're already doing is structurally the correct approach to delete a large volume of sObject records:
Extract the data to be deleted (just the Ids).
Load the data into a Bulk API delete job.
The one key thing I don't see in your post is whether the Data Loader is actually configured to use the Bulk API. It can use either Bulk or SOAP APIs. The ...
I have not found a reference in the release notes regarding which release introduced this functionality, but in the following image you can see an order number in order to set the duplucate rules execution order. It works!
Is there a particular order in which they are executed?
The order is undocumented, and may change from release to release or as changes to rules are made.
or is it random?
It's not "random" so much as "indeterminate." The system will run the rules in the same order for a while until conditions change, in which case the order may change. What causes the ...