How to send a notification in the Flow Designer when it's before a certain date

Mi1
Tera Contributor

Hi,

I want to set a condition in the flow designer to send a notification "six months after the flow execution time".

However, the flow designer could not find such a condition.

I'm thinking that I need to have a script in my Look Up Records action that runs before a certain date.

Please let me know if there is any other appropriate way.

Regards,

1 ACCEPTED SOLUTION

Soeren Maucher
Mega Sage

Hello @Mi1

 

in general it would be possible to add a "Wait Condition" to your flow as a second last step and then as a last step send out an email. This way you could send out an email a certain time after the rest of the flow has been finished. 
5.PNG

In your case, however, the time with 6 months is rather long and the flow will stay in a waiting state until the 6 months are over. This will probably result in many open flows which is not good for the performance and in general could potentially lead to issues if you change the flow logic or perform an instance update/ upgrade. 

 

In general, I would therefore suggest, that you add on your underlying record (maybe incident/ change/ case / contract ...) a notification date. As a last step of your current flow you can set this date based on todays date plus 6 months. 
Then you build a second sheduled Flow running each day at for example 1 am, which does a lookup on the underlying table (incident/ change/ case / contract ...) and returns all records with notification date = today. In this flow you can then itterate over all the returned records and tigger an individual notification. 

 

I hope that helped! 

 

Greetings, 
Sören

 

 

View solution in original post

1 REPLY 1

Soeren Maucher
Mega Sage

Hello @Mi1

 

in general it would be possible to add a "Wait Condition" to your flow as a second last step and then as a last step send out an email. This way you could send out an email a certain time after the rest of the flow has been finished. 
5.PNG

In your case, however, the time with 6 months is rather long and the flow will stay in a waiting state until the 6 months are over. This will probably result in many open flows which is not good for the performance and in general could potentially lead to issues if you change the flow logic or perform an instance update/ upgrade. 

 

In general, I would therefore suggest, that you add on your underlying record (maybe incident/ change/ case / contract ...) a notification date. As a last step of your current flow you can set this date based on todays date plus 6 months. 
Then you build a second sheduled Flow running each day at for example 1 am, which does a lookup on the underlying table (incident/ change/ case / contract ...) and returns all records with notification date = today. In this flow you can then itterate over all the returned records and tigger an individual notification. 

 

I hope that helped! 

 

Greetings, 
Sören