You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has anyone else ran into the error message listed below when importing records into the Salesforce "Interaction" object using an ETL tool?
"OBJ: Interaction__c - INT_Interaction: System.LimitException: Apex CPU time limit exceeded"?
We needed to break our Dell Boomi process to include batch sizes of 12 to handle the PeopleSoft records, as anything more than 12 records included in the batch prompted the error message above
Looking for feedback on possible approaches to help alleviate this issue other than breaking it up in to these small batch sizes
A common cause for this: The amount of related automations occurring as result of the interaction insert is too much for the SalesForce governor. To verify, try a test load with related workflows/process builders/flows turned off for related objects, and see if that improves the CPU time limits (perhaps the batch can be larger).
If eliminating automations improves the data load, it might be wise to refactor those automations to occur within a scheduled batch (if business procedures allow it).
Hi Everyone,
Has anyone else ran into the error message listed below when importing records into the Salesforce "Interaction" object using an ETL tool?
"OBJ: Interaction__c - INT_Interaction: System.LimitException: Apex CPU time limit exceeded"?
We needed to break our Dell Boomi process to include batch sizes of 12 to handle the PeopleSoft records, as anything more than 12 records included in the batch prompted the error message above
Looking for feedback on possible approaches to help alleviate this issue other than breaking it up in to these small batch sizes
Thanks in advance,
Jason
@karamcintyre @jacebryan
The text was updated successfully, but these errors were encountered: