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
Lars NielsenLars Nielsen 

Apex CPU limit errors seem to have risen dramatically with Winter '16 and beyond

In all the orgs I have investigated so far (a few hundred) it all comes down to the Pocess Builder from what I can see. It is almost like the process builder is not catching the CPU limit and then the moment it hits a managed package it just throws the exception. 

I am seeing people doing a lot of dangerous recursive stuff in the process builder that would normally never fly if you did in Apex but somehow it works and then the next thing down the line pays the price. Anybody else seen similar issues?