CPU issues caused by process builder and workflows has really gotten bad in last 3 releases
In my case it is a managed package. I can uninstall my package and the next package in line hits the limits on entrance.
From everything I can tell it is like the process building and visual workflows are allowing people to build what end up being very poorly writing code behind the scenes (crazy recursion etc) and not respecting the CPU limits but upon exit all of a sudden any custom trigger pays the price.
Love to get others feedback.
Exit workflows - message
Maximum CPU time: 17895 out of 10000 ******* CLOSE TO LIMIT
Enter managed package - set one single variable - just a boolean
CPU limit exceeded
Last time I checked that should have thrown an excpetion before it got down the chain any further. So is Salesforce just exempting the users from the limits in Process Builder? If so that makes like hard for anyone else after those processes get complete.