Prevent Recursion/CPU Limit in Process Builder

Question

I have a Process Builder that I created which is working fine in my lower sandbox but is throwing a CPU Limit error when deployed to production. I have used IsChanged in the process builder. I think whats happening is that each time a value in the component is changed, it executes the calculation, but when the component is changed, it always evaluates to true so I think it is entering a recursion loop. Is my theory correct? Do I need to modify the process builder to make this work. Basically what I am trying to do is when a component in an equation is changed or modified then the "Rating" field is recalculated and updated. I have attached some pictures of my process builder

AND(
    NOT(ISBLANK([Opportunity].LPP_Rating__c )),
    TEXT([Opportunity].Collection_Status__c) <> "Open",
    [Opportunity].Retake__c = false,
    OR(
        ISCHANGED([Opportunity].Total_Payments__c), 
        ISCHANGED([Opportunity].Sales_Tax_Rate__c),
        ISCHANGED([Opportunity].Reorder_Payments__c),
        ISCHANGED([Opportunity].Total_Production_Value__c),
        ISCHANGED([Opportunity].Discount__c),
        ISCHANGED([Opportunity].Children_Photographed__c),
        ISCHANGED([Opportunity].Commissions_Paid__c)
    )
)

The formula is basically several if else statements (if equation is greater than .62 then update Rating fiels to "A" and so forth). I intially had selected "No criteria-just update the records." I changed it to updated records meet all conditions" Can you please let me know if this should finish the CPU limit error and if I should modify it further? Thanks

Answer 1

This can all be achieved with a custom formula field (see how to create one here) and you can avoid Process Builder altogether.

Add all these conditions to the formula field, and anytime conditions don't match properly, you can put the value as null so it'll be blank for situations in which there shouldn't be a rating.

If you need this rating to be static and unchanging at the time it's set (and not always updating with changing conditions), have the same formula field in the background (i.e. take it off any of the page layouts) and use Process Builder to simply set the normal Rating custom field to the Calculated Rating custom formula field.

Answer 2

Simple answer - Don't use PB

PB is a fancy tool that can leverage Workflow field update logic. However tool is not perfect and might cause issues, especially when used on vital SFDC object as Opportunity. I suspect that you have multiple managed packages on top of Opportunity object or multiple workflow updates. Even Dan Appleman doesn't recommend to use PB, cause its slow and unpredictable.

Try to replace it with:

• before trigger if you need to update source object.
• formula field if answer is based on oppty fields