Parallel Approval Flow with Status of each approval task

[danmitchell36]

I am currently working on a Flow that runs on a list in SharePoint. The Flow is triggered manually and when it is triggered sends an approval task to every person in a multi-person field. The number of people in the field is variable (usually between 4 and 20). 

Currently, this works great except for when one person doesn't respond and there is no way of knowing who still has an outstanding approval task since the Flow pauses until every individual has responded. 

Has anyone found a good way to overcome this?

[v-bacao-msft]

Hi @danmitchell36 ,

Could you share a screenshot of the Flow configuration?

According to your description, Approval action seems to be configured in Apply to each, using each person in Person field as Approver.

You could try to append all person emails into a String variable, and then configure the variable in Assigned to field, as if this can achieve your needs.

Image reference:

Best Regards,

[danmitchell36]

@v-bacao-msft ,

Thanks for responding. What you described is what I did. The Flow works but I need insight into which of the approvers has not approved the item at any given time.

I have thought about having the approvers in separate fields and running separate Flows for each of them but given the number of approvers can be variable this doesn't seem like a great solution. I'm looking for advice on how to track who has and has not approved an item before the Flow finishes.

Does this make sense?

[v-bacao-msft]

Hi @danmitchell36 ,

The feature you mentioned is currently not available for Flow. It seems that you have submitted your suggestion on the Ideas forum.

I will also recommend more users with similar needs on my side to vote for this idea.

Best Regards,

[Anonymous]

Actually, if i am not mistaken, you can get this work with using the "concurrency control" option of the for each loop. Just activate it and the approval task will not run sequentially but in parallel..

[asssssssssssss]

Do we have to vote for that function? Isn't it the basic thing MS should thought about? what kind of design is that?