Recurrence as an action not a trigger

[Anonymous]

Hi Guys,

right now I am implementing a flow where every day I need to check all SP list item if certain criterias are met. If so, I use a Switch control to branch the several possibilities.

Within several of these possibilites I want to implement recurrent reminder mail flows. For one this is

• one day before due date
• at due date
• after due date
• then every 30 days

For another possibility it is just weekly. I dont want to implement all the time a new flow. I want everything compact in one flow. Even then I need still to check all the time everyday which status has every item and depending on that branch the flow.

Hope you could help because the only thing I could do is to delay the workflow but I don't know how to do that.

Right now I am solving this with a several counter for every status, the flow increment the counter if it is still in the same status and if a certain number is reached (counter = 7 --> 7 days) the condition is true and a mail is sended out. But as you see this is not really dynamic. I have to hard code the switch cases (7, 14, 21, ...).

So, I thought, hey this should be easy because weekly just means multiples of 7, monthly means multiples of 30. But how can I use that? Does someone know how to define multiples of a variable in a condition?

Hope you can help me and drop me a message if you need anything else.

Best regards,

Pitfrog91

[AKRogers]

Hello!

Have you tried the Delay or Delay Until actions?  You can use these to delay a Flow by a certain number or hours, days, months etc., or to wait until a specific datetime to excute the rest of the Flow.

Take care,

Ashley

If this response provided an answer to your question please mark it as a solution. Thank you!

[ScottShearer · Accepted solution]

@Anonymous 

One way of attacking your issue might be to use a recurrence trigger that fires once a day.  When the trigger fires, use a Get items action to retrieve the list items.  Then, loop through each item and test for each of your conditions and take action as appropriate.

Another way might be to create a Flow for each of your conditions.  The Flow should fire on a daily basis.  Then, use a Get items action with an OData filter so that only those items the meet the specific condition are returned.  Here is a link to a blog post that shows how to filter SharePoint list items with an OData filter.

[Anonymous]

@AKRogersthat won't help me. it feels that the delay functions is too static for me and doesnt provide me a recurrent function.

@ScottSheareri am already doing it exactly how you stated it. but still i need to hardcode the recurrent function. but nevermind it does the trick and for the business process it is more than sufficient. 

Thank you very much 🙂

[PowerExplorer]

I think mine is slightly a different issue than the stated above . Mine is the "Get Items' action. It sends multiple items in one email and sends duplicated emails if the conditions are met. But my req is ' Send different tasks(items) at different frequency to different audiences '. 

I want each item to be sent separately not in bulk. Also I want to pause if there is no task this month or week. I think the pic below would make my requirement a bit clear.

Req 1, IF 'pause' is selected in SP choice field don't trigger , IF 'Make this a repeating event' is selected trigger the flow.   

Req 2, IF the item is submitted as a 'Weekly ' task Send email every week with info pulled from SP but don't send all the items that meet that criteria in bulk (in one email). Instead one email per one item. If there are 3 monthly items /tasks submitted in the SP list It has to be emailed separately. 

[PowerExplorer]

Attaching here the rest of the pics