cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Chelsa
Frequent Visitor

Parallel approvals, one email

I tried searching the baords, but haven't found anything that quite matches what I am looking for, so I am hoping to get some help!

 

I have an approval workflow that triggers on an item being created in a list (Change Request for Project Scope)

 

There is a condition applied after the trigger so that if a condition is not met, no approval workflow fires.

 

But when it does, I have two parallel approval flows (one for QA Manager, one for the Domain Manager). The rule is, if your CR has not been approved by BOTH approvers, you can't come to the Change Meeting. 

 

Rather than spam the user with an email for each approval (and potentially causing confusion cause they see one email that says "Approved" and assume that means they've met the meeting attendance criteria), I want one email to fire after both approvals have happened. 

 

Would I just have the two flows and underneath the two, a condition (if QA response = Approved), then another condition in the "If yes, then" section underneath (if Domain response = Approved) --> Action "Send an Email"? Would that work? If there's a sizable delay between when the QA person approves vs. the Domain person approving, will that cause the the flow to error out instead of sending the email?

Would it work better if I ended this first workflow after the New Item is updated with the approved/rejected responses, and set up a second workflow that fires off an email once the 2 approval conditions are met? Anyone got ideas on the best/most efficient way to do this?

1 ACCEPTED SOLUTION

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @ Chelsa,

 

Are the Approver under your SharePoint list the People or group type?

Using nested conditions should be able to achieve your needs. I have made a test on my side and it works well. The screenshot of my test as below:
1.PNG
2.PNGThe flow works successfully as below:3.PNG

In Microsoft Flow, there is a limit in run duration of a flow. The max run duration is 30 days. If the sizable delay that you mentioned within 30 days, the flow will work well. Otherwise, the “Start an approval” action will time out and may cause a time out error instead of sending email.

 

 

More details about limits of run duration of a flow, read the article as below:

Run duration and retention

 

Best regards,

Kris

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
v-xida-msft
Community Support
Community Support

Hi @ Chelsa,

 

Are the Approver under your SharePoint list the People or group type?

Using nested conditions should be able to achieve your needs. I have made a test on my side and it works well. The screenshot of my test as below:
1.PNG
2.PNGThe flow works successfully as below:3.PNG

In Microsoft Flow, there is a limit in run duration of a flow. The max run duration is 30 days. If the sizable delay that you mentioned within 30 days, the flow will work well. Otherwise, the “Start an approval” action will time out and may cause a time out error instead of sending email.

 

 

More details about limits of run duration of a flow, read the article as below:

Run duration and retention

 

Best regards,

Kris

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Before this response, I did something very similar, expect instead of using a Condition, I used a "Do Until...".

 

For folks reading this thread, DO NOT use a "Do Until". Hahaha. There was a delay between the first and second approval of 2.5 days. The "Do Until" command essentially generated a new email every 60 minutes, so that when the second approval came in, it fired off approximately 62 "Your item has been approved!" emails to the submitter and the 2 approvers. 

 

I've now removed that and replaced it with a "Condition", and that seems to have done the trick! If I encounter any more issues now that this form is live, I will come back to update this thread 🙂

 

Thanks!

Helpful resources

Announcements
Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Top Solution Authors
Top Kudoed Authors
Users online (2,948)