1

Execution Overview

In the Execution logs, Profiling information shows a managed package visualforce method executed for 35,256 ms. But the APEX CPU Limit is 10,000 ms. How is that possible.

PS. I am debugging APEX CPU Timeout Issue. My managed package is dependent on another vendor's managed package.

10
  • I've explained this before, as well as Derek F. Basically, the system can choose when, or if, to terminate your request at its discretion based on available resources. It's unlikely, but possible, that a transaction could run as high as 30,000 ms. You'll probably need to get managed package debugging enabled in order to figure out why this is happening. – sfdcfox Feb 17 '17 at 1:46
  • 2
    Process builder is immune to CPU time limit. it can run for longer than the 10K ms and then the next line of code that is hit will error. Is this the case here? Idea is package causes a DML and PB is fired then upon return to the controller bam, CPU time limit exceeded – Eric Feb 17 '17 at 1:50
  • @Eric Excellent point, that. PB can easily run that long without causing a timeout until you get back into Apex Code territory. – sfdcfox Feb 17 '17 at 2:18
  • @eric and sfdcfox, thanks for input. I have de-activated all the workflow rules and process builder flows and I still see the error. Although the processbuilder and workflow rules are now contributing to a negligible percent of time, I just deactivated every single one of them to rule them out. – Venkata Feb 17 '17 at 2:29
  • Can you include a screenshot? Real time elapsed can be significantly more than CPU Time consumed. – Adrian Larson Feb 17 '17 at 2:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.