process-buildersalesforce-flow
The flow has multiple nodes and several scheduled paths, the original process looks like this:
and this is how far I have come:
I am wondering how to link the paths without affecting actions that have only a one-time occurrence… and achieving the result that the process is serving.
This is the process limit. You can refer it.
You will hit the limit but you can still use them. Once Salesforce reach the limit it carries forward them into next hours and Salesforce take care of it.
The short answer is NO; the new flow version's entry criteria gets applied to pending scheduled paths generated by prior flow versions
I did an experiment:
Is_FieldA__c = TRUE and two actions to send emails at +7 and +14 daysMyRecord that met entry conditionsRESULT:
Setup | Time-based Workflow shows 2 pending entries for +7 and +14 days for record MyRecord
I then updated the Flow to Version 2 and added an additional entry condition such that the emails get scheduled when
Is_FieldA__c = TRUE AND Is_FieldB__c = TRUEUpon updating MyRecord such that FieldA was TRUE but FieldB was FALSE...
RESULT:
Setup | Time-based Workflow shows 0 pending entries for record MyRecord
That is, changing the flow version and amending the entry conditions in the new version will apply to records that scheduled elements under prior versions - thus enabling one to introduce new criteria over time to remove in-flight scheduled actions and not needing to resort to the complexities associated with Process Builder.
I surmise this works because Scheduled Paths on record-triggered flows come directly out of the flow's entry conditions. In Process Builder, you can have many decision criteria nodes, some of which are attached to Scheduled Actions. Thus, when the Process Builder changes versions, SFDC essentially assumes the entire old Process Builder is effectively NOP and the only thing Salesforce will do is accelerate/defer the scheduled events of the old version if the underlying reference date changes.
After you deactivate a process, the scheduled time for pending scheduled actions stays the same. If a deactivated process has pending scheduled actions and the record whose field the schedule is based on is changed, Salesforce recalculates the schedule for those actions. After a process is deactivated, Salesforce ignores all other changes to the associated records."
Best Answer
I resolved this by using a decision node with multiple actions per decision instead, given that each action is unique. Each decision was then matched to its corresponding scheduled path.
The only downside is, that when some of the decisions fall between both paths I had to repeat those, ain't seen a better way around that yet. Perhaps in the future, as I gain more experience.