Avoiding "Same Branch" Re-entrancy on Process Builder

Question

When you develop Triggers you can avoid re-entrancy by keeping track of ids in static variables of your Apex Classes, however when dealing with process builders it is not obvious to me how to avoid publishing an event multiple times.

In particular, I have a branch that is executed upon these conditions:

ISNEW() || ISCHANGED([MyCustomObject__c].MyField__c)

What seems to be strange is that in the same transaction ISNEW() this branch is executed four times: one solution would be to avoid re-entrancy for the same record, but I need it for some other branch of the process builder. What is the best practice to avoid "same branch" re-entrancy?

Answer 1

Try turning off the process builders recursion setting in its advanced options (that is, disabling ‘evaluate a record multiple times in a single save operation’)

Source: https://help.salesforce.com/articleView?id=process_advanced_considerations.htm&type=5&sfdcIFrameOrigin=null If your process uses the ISNEW formula function and reevaluates a record multiple times in a single save operation, the process may execute actions multiple times. For example, your process checks whether an account is created or updated.

Docs example claims “When ISNEW evaluates to true, the process updates the account’s annual revenue and posts to Chatter. When the process updates the account’s annual revenue, the process then reevaluates the record (up to five additional times) because the record was changed. Each time the criteria is evaluated, ISNEW evaluates to true”