Loading

Account Engagement Prospect Sync Error: "Apex CPU time limit exceeded"

Publiseringsdato: Sep 30, 2025
Beskrivelse
The ‘Apex CPU time limit exceeded’ message indicates that the time it’s taking for Apex code to execute in Salesforce is longer than the acceptable limit for the Maximum CPU time on Salesforce Servers. More on these limits can be found in our documentation.

However, this is almost always due to a “team effort” from multiple triggers running at the same time. Account Engagement won’t be using up all these resources, but may be the process that is running when the limit is broken. This could result in Salesforce referencing Account Engagement's trigger in the error.
Løsning
We recommend enabling debug logging for your Account Engagement account’s Connector user, as outlined in this article.
The following debug levels are recommended: 
Database → Info
Workflow → Fine
Validation → Info
Apex Code → Fine
Apex Profiling → Fine
VisualForce → None
System → Debug

After enabling debug logging, attempt to reproduce the error again. After reproducing, in the quick search in Salesforce Setup, type in ‘Debug’.
— Select ‘Debug Logging’.
— Beneath the debug flags you will see a list of files.
— Look for a file with a status of ‘Apex CPU time limit exceeded’.
This should contain more information on the resources being used. 

Chances are, other Apex classes/triggers will need to be optimized, as described here. It’s not always guaranteed, but you can make some informed guesses as to which triggers are taking up the most time based on logs from Salesforce.
Knowledge-artikkelnummer

000388822

 
Laster
Salesforce Help | Article