I have a flow that contains a sequential approval process. Approval process is contained within an Apply to Each. Upon 30-day flow timeout, if the flow is still within the Apply to Each (waiting on an approver response), the flow does not "end" in the way expected...instead, it is completing the operations of the Apply to Each, which means it cycles through the remaining approvers, sends them approval request emails (which are invalid), and only *then* does the flow actually end. This is very confusing and irritating for end users.
I don't understand how this could possibly be the intended behavior of the flow upon timeout. Has anyone experienced anything similar, or are there any quick fixes anyone can suggest?
Could you share a screenshot of your flow to help reproduce this issue?
From your description, it seems that there are multiple approval processes within Apply to each, while the time out of the first approval process doesn’t end the flow, it is completing the other actions of the apply to each.
I have made a simple flow likes below to reproduce this issue, however, the issue you mentioned didn’t occur. Once the first approval timed out, the flow failed.
Please feel free post back with more details on the flow.
Could you share a screenshot of the run details?
Does the first approver give a response?
I will set up a flow according to your description and wait for 30 days for testing.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!