Visual Workflow – Do Scheduled Paths Based on Date Fields Get Re-evaluated if the Date Changes

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:

• Create a Flow Version 1 with entry condition: Is_FieldA__c = TRUE and two actions to send emails at +7 and +14 days
• Created an object with name = MyRecord that met entry conditions

RESULT:

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 = TRUE

Upon 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.

Side bar

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.

What Happens When the Associated Process Is Deactivated?

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."

Entries in the Setup | Time-Based Workflow using every time a record is updated and meets the condition requirements

Appear

• When the record matches the Flow's entry criteria. And only the first time unless DML causes the record to no longer qualify for entry (see Disappear) at which point the next time DML occurs to satisfy the entry criteria, a new TBW is created from the scheduled path.

Disappear

• When the record no longer matches the Flow's entry criteria or
• When the time trigger transpires and the scheduled path executes

Adjust

• When the reference date(time) of the scheduled path changes value on any DML operation.

Once the record has already generated the TBW events, changing any other field value on that record will not cause the flow to even execute, let alone any new TBWs to appear.

To solve your issue, some options:

• Use created and every time it is edited (which can lead to many, unintended TBWs)
• Have a separate Flow to handle the additional field, perhaps using subflows to handle shared logic