Kel Woodbury - 10 months ago
This is rediculous, we just ran the SALESFORCE OPTIMIZER REPORT to see if it could identify problems with slow Account updates, and it marks our workflows and triggers as problems and recommends we create more process builder flows to help out the issue. So we are checking in our full sandbox and turn off all of the workflow and triggers and it didn't help at all. Curious we turned off the Process Builder flows and all of the problems are gone. Why is Salesforce pushing a feature that creates more performance issues?
James Clayton - 1 year ago
Same issue as others. Without internal developers, we used Process Builder for numerous automation needs. Consultants wrote code where process builder was insufficicient, then they received CPU limit error and told us the Process Builders were the problem. We converted all of those process builders to Apex, at a significant expense. So much for "clicks not code".
Edward Yerke-Robins - 1 year ago
As a system admin who can't code, I went all in on the idea of Process Builder as fully "clicks not code" automation. Recently, I installed an integration with our email marketing service, and the combination of their Apex & our Processes began to receive CPU timeout errors. Their developers found the issue was with our Processes, and recommended converting them to Apex triggers. This is something I can't personally do, and as a nonprofit I don't know if I have the budget to hire someone to do it (I also as an admin want to avoid the situation where I'm "on the hook" for non-app customization that I can't understand/fix).
If you'll excuse the melodrama, I feel betrayed, because now I've had to turn it all off, so I look like the bad guy when my colleagues ask why all that awesome automation I set up isn't working. If there's any possible way you can improve Process Builder execution, it would certainly make us happy again :)