New answers tagged

1

Sid's suggestion of deactivating the failing Flow/Process Builder is a valid one. However, our organization has multiple processes running on one record. I was able to solve this and have my bulk update process without any errors by changing the Batch number to '1' instead of the default '200' - Solution located here.


0

This may be because your queue is not configured to be used on Tasks. If this is the case, you need to edit the queue and add "Task" to the supported objects.


0

There is a Flow/Process Builder in your org, with the API name "System Pick - Update System_Pick_at_First_System_Rec" What you need to do is deactivate this - attempt your data load and then reactivate it. It seems to be running for more than one records in your batch and invoking multiple recursions that are attributing to this limit.


1

From the above screenshot it seems that 'Customer Success Manager' is a lookup to the User Object. What you can do is, since you have the Customer Success Manager in name form, you could run a query for those against the User object and get the Ids for each of those names. Then in your initial AccountId->Customer Success Manager Name, replace the name ...


Top 50 recent answers are included