Apply to each is restricted by approval process

[navaidm]

Hello Community

I am trying to make a flow which

1. gets a share point list
2. Uses apply to each to iterate through each item
3. Applis condition to check if the date in a column matches a certain value
4. If the date field matches a certain value then starts an approval process where approver is the person in the item
5. sends email to designated person about approval response

The problem is that "Apply to each" only iterates after a response is rcvd from last approver.

Although this is technically correct but this is not the logic that needs o be applied. 

Approval should be started for all items at same time and shoud not wait for one item to complete before starting the next one in list.

Any Ideas for a work around ?

[Piper · Accepted solution]

Apply to Each loops iterate sequentially by default; you can change the concurrency of Apply to  Each under the Settings of the Activity. Here's some screen shots to get you there:

[navaidm]

@Piper Tnx a bundle..Works like a charm..gr8

[kristof805]

@navaidm @Piper 

I actually am running a similar Flow to the one discussed here and have a question on capturing the approvals and a question on having the Flow time out.

My Flow is:

1. Recurrence Trigger (midnight)
2. Get items from SharePoint List
3. Apply to each Value -> if condition is met (SharePoint item date is seven days away)
4. If Yes -> Create an approval (v2)

I'm not really sure how to finish the capturing of the multiple approval processes just yet. Would I switch over to Start and wait for an approval (v2)? Then based on the outcome I can update each SharePoint List item that was approved with the date / time / person.

I have not been able to test the concurrence settings suggested by @Piper as the Settings button is currently not working.

Is there any way to have this Flow time out manually after a set amount of time?

[Piper]

@kristof805 I think your idea for the flow is sound. You should be able to create the flow and then fix the settings once Microsoft fixes the bug.

Flows themselves timeout after 30 days, but you can configure the timeout settings on a specific action. Here's a link to a blog post, How to use a timeout for your Microsoft Flow approvals, that should get you going with that. Then you can configure the run after timeout.

Here's some screenshots of how I'm doing that. One thing I ran into is that it will error out my flow of there is a timeout. I'm pretty sure I just need to add a Terminate action and set it to success (I just haven't implemented it yet).

Configure Run After

Should run after timeout

Run Failed after Timeout