web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Continue flow after Ap...
Power Automate
Unanswered

Continue flow after Approval request if response from all recipients not yet received

(0) ShareShare
ReportReport
Posted on by 6

Hello forum,

 

I currently have an approval flow set up where it requests approval from ALL recipients. However, there will be cases where I do not get a response from all recipients. Is it possible to wait x amount of days before j using the responses received 

Categories:
I have the same question (0)
  • okeks Profile Picture
    802 Super User 2024 Season 1 on at

    You can actually read the already given responses from the Dataverse Table with a query to filter on the ID of the approval.

     

    In that case you first create the approval.

    Then instead of using the "Wait for an approval" you put a do until with a simple variable varApprovalDone as condition.

    Inside this loop you first place a delay action with a set time, e.g. 1 minute.

    Below this also inside the loop you put List row on dataverse for the previously created Approval.
    Then you put a condition where you check if either the approval is done or the "Countdown" is expired.

     

    Then outside the loop you List the rows of the Approval response table of dataverse which belong to your approval and can work.

     

    It is definitely not easy but doable.

     

  • okeks Profile Picture
    802 Super User 2024 Season 1 on at

    and here are the tables you need:

    okeks_0-1668690785807.png

     

  • grantjenkins Profile Picture
    11,063 Moderator on at

    What do you want to happen if not all of them respond within x time and you continue your flow? I mean, will the approval be treated as Rejected, Cancelled, or still Approved? And how long do you expect x to be?

     

    I would set a Timeout on your Approval and have a Parallel Branch. One that runs on Success (all approved) and one on Timed out (not all approved).

     

    See example flow structure below.

    grantjenkins_0-1668782706234.png

     

    Note that we don't use Start and wait for an approval as we won't be able to get the Approval ID if it times out. We instead use Create an approval and then Wait for an approval. This way we can get the Approval ID from Create an approval since this will be successful and only the Wait for an approval will potentially time out.

     

    Create an approval will start the approval.

    grantjenkins_1-1668782892370.png

     

    Wait for an approval will wait until the approval has been fully completed. For this we go into Settings and set a Timeout period to suit your requirements. In my example for testing purposes, I've set it to timeout after 1 minute - PT1M.

    grantjenkins_2-1668782913406.png

    grantjenkins_0-1668816299267.png

     

    I would then add a Scope for the success branch (if all users approved). Then add a parallel branch and add another Scope to be used when the Wait for an approval action times out.

    grantjenkins_1-1668816432990.png

     

    On the Scope NOT All Approved we would go into Settings > Configure run after and set it to has timed out.

    grantjenkins_2-1668816537071.png

     

    If Wait for an approval is successful it will go to the Left Branch. This means that all recipients have responded.

     

    If Wait for an approval times out it will go to the Right Branch. In here you can get the Approval ID and set the approval in Dataverse to Cancelled or Timed Out which will ensure all existing Approval Tasks that are still with the original recipients will see that the approval has completed. Otherwise, their Approval Tasks will still look like their active and even let them add comments and click on Approve or Reject.

     

    Note that because you are running Scope NOT All Approved via a time-out, you will need to add a Terminate at the end and set it to Succeeded, otherwise the flow will look like it failed even if it actually succeeded.

    grantjenkins_3-1668816673227.png

     

    Below might be what your Scope NOT All Approved action might look like if you are also updating your Approvals table in Dataverse.

    grantjenkins_4-1668816750430.png

     

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard