3

We want to create an Asynchronous path on our Account - After Update Record Triggered Flow. In order to do so, we must specify entry criteria identifying what changed before the system will enter into that Flow. If not, this error will occur when saving the Flow:

enter image description here

We are using Record Trigger after update Flows as a dispatcher to call other subflows. However, we'd prefer to use something like LastModifiedDate or SystemModstamp so that any/all record updates enter this Record Trigger Flow, including the Asynchronous Path. We have found that using LastModifiedDate and SystemModstamp in the Start entry criteria do not result in the Flow firing. Perhaps these fields are not updated yet when the system evaluates them to enter the Flow. So, does anything have any suggestions on how we can cause the system to enter the Flow to enter on any/all record updates?

Thank you.

8
  • why use any criteria at all? Just choose None
    – cropredy
    Aug 3, 2022 at 0:59
  • @cropredy we tried that, but apparently one must specify criteria to enable an async path on an after update record trigger flow. Aug 3, 2022 at 16:13
  • Can you use a formula that evaluates to TRUE?
    – cropredy
    Aug 3, 2022 at 18:25
  • @cropredy thanks for the suggestion, but this does not work. I added some more detail related to my question regarding this. Aug 3, 2022 at 20:33
  • Well - hack city - a before save flow that increments a Counter__c field by 1 should allow you to use an Is Changed operator in the after save flow. But my suggestion seems prima facie silly.
    – cropredy
    Aug 4, 2022 at 0:47

1 Answer 1

1

This works for me once the Account was created, every change thereafter to the Account caused a Chatter message

enter image description here

entry conditions Last Modified Date Is Changed TRUE enter image description here

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .