function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Candice Chu 19Candice Chu 19 

Process Flow Error

We are currently having issues in our environment where we've gone and created 2 Process Builders pulling from Task and then updating on the Contact.  

Error element myRule_1_A1 (FlowRecordUpdate).
The flow tried to update these records: 0032A00002VB8EmQAL. This error occurred: ALL_OR_NONE_OPERATION_ROLLED_BACK: Record rolled back because not all records were valid and the request was using AllOrNone header. For details, see API Exceptions.

More so, we are having issues with the flows when lead conversion happens.  

Error: System.DmlException: Update failed. First exception on row 0 with id 00T23000005q7a7EAA; first error: CANNOT_EXECUTE_FLOW_TRIGGER, The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301230000000VKM. Flow error messages: <b>An unhandled fault has occurred in this flow</b><br>An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.: [] Class.leadconvert.BulkLeadConvert.updateLeadTasks: line 1279, column 1 Class.leadconvert.BulkLeadConvert.convertLead: line 127, column 1

We've concluded that we get these errors when the Lead has more than 10 or 20 tasks related.  Those tasks in particular are the ones that trigger our Process Builder.  

We tried to diagnose the issue in Sandbox as well.  Based on posts I've read it's possible that we are hitting limitations

Does anyone have any suggestions aside from creating an Apex Trigger to do this?  

Akhil AnilAkhil Anil
Hey Candice,

How are you updating your leads for the process to kick off ? Through the data loader ? If yes, then try setting the batch size to 1 in data loader.

Hope that helps !
Candice Chu 19Candice Chu 19
HI Akhil,

This actually happened during a manual lead conversion on a lead but orignally triggered when our platform that feeds into Salesforce triggers the conversion on the backend.  
Candice Chu 19Candice Chu 19
The flow that we get an error for is related to Contact object but the records are leads because they are rolling back. Any ideas how we can fix our flows?