11

I uploaded a .csv file with 50000 rows to the Salesforce Workbench to update a custom field in Opportunities. For most records I got the error

Too many lock failure 200 Trying again later.

I tried the same in the Data Loader, and it worked fine.

Although my update succeeded, I would like to understand what the difference is between the Workbench and the Data Loader. In the Workbench the checkbox Process records asynchronously via Bulk API was ticked and I left it ticked. I thought the Data Loader is another Bulk API client. What could be the reason why they behave differently? Is there a general difference between the Data Loader update and the Workbench update with the Bulk API checkbox ticked?

Improve this question
2
  • I guess workbench operated in Bulk API - Parallel processing mode. Parallel processing mode is known to throw these errors. In Dataloader, you have to manually select the BULK Api option and if you don't, it operates in SOAP/REST API mode.
    – javanoob
    Feb 8, 2017 at 12:18
  • This answers my question, thanks. I'll mark it as the solution if you make it an answer. I didn't know the option to use the Bulk API.
    – Stefan Berger
    Feb 8, 2017 at 12:52

1 Answer 1

Reset to default
8

As you mentioned in the Question, I guess workbench operated in the Bulk API but in Parallel Processing mode. Parallel Processing mode is known to throw these kind of errors. Refer to the section Managing Locks to Maximize the Benefits of Parallelism in this The Salesforce Bulk API - Maximizing Parallelism and Throughput Performance When Integrating or Loading Large Data Volumes

Also, in Dataloader BULK API is not enabled by default. We have to go to settings and check the checkbox. Because you did not, I guess it operated in the SOAP/REST API mode.

You can even go to your org and check BULK Data load jobs section to make sure those 50000 rows did not use BULK API.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .