Skip to main content
Community site session details

Community site session details

Session Id : DAQvFzeSKwdc8IgQeK2hPD
Power Automate - Building Flows
Answered

Use cases for "Start..." --> "Wait for an approval" VS "Start and wait for an approval"?

Like (0) ShareShare
ReportReport
Posted on 4 Dec 2019 23:02:04 by

I'm a bit confused about when to use these related actions.

12-4-2019 4-38-48 PM.jpg

Is my commentary accurate? Are there other differences?

 

Specifically, I am trying to capture status and comments from a list of reviewers, in more-or-less real time.

The following pattern (shared by other selfless experts in this forum) works pretty well:

12-4-2019 4-49-24 PM.jpg

but it only writes the responses back to my SharePoint library properties at the end of the entire Approval process; i.e., after every Reviewer has responded.

 

I am thinking of experimenting with combinations of:

  • a Parallel approval process
  • "Start", then "Wait" -- or "Start and wait"
  • collecting and evaluating the Approved/Rejected results of each parallel process to mimic "Wait for all responses" to ultimately approve or reject the submitted file

Would any other selfless experts care to offer their hard-won experience in reply?

  • Pstork1 Profile Picture
    67,158 Most Valuable Professional on 05 Dec 2019 at 03:58:45
    Re: Use cases for "Start..." --> "Wait for an approval" VS "Start and wait for an approval"?

    Just to add to my reply.   Using either action to create and wait for the approval works the same way.  You'll need to do each approval separately in a parallel branch.  All the parallel branches will need to finish before the flow will be able to move on.  But you will be able to do things inside each branch to react to the individual approvals.

  • Verified answer
    Pstork1 Profile Picture
    67,158 Most Valuable Professional on 05 Dec 2019 at 03:48:37
    Re: Use cases for "Start..." --> "Wait for an approval" VS "Start and wait for an approval"?

    If you create an approval that has multiple approvers then neither pattern will let you do anything with the replies until after everyone has replied.  The reason both patterns are supported is because occasionally you want to do other things with the approval details before sending the approval or want to do something with the approval in a parallel thread. 

     

    For example, a common request is to be able to send a reminder with a link to the approval if its not completed within a particular timeframe.  Sending the reminder is easily done in a parallel branch, but you need a reference to the approval itself to be able to send a link in the reminder.  So you create the approval, then create the parallel branches.  In one branch you wait for the response and in the other you do the reminder after a pause. Unless you create it before entering the parallel branch you won't be able to send a link.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 2

Loading complete