Showing results for 
Search instead for 
Did you mean: 

Run After Action Timeout counts as Failure?



So I've recently put together a flow that has a timeout catch parrallel branch if the proceeding action times out / doesn't receive a response. 


This parrallel branch is doing it's job and runs fine, but the flow gets marked as Failed because the previous actionable piece of the flow timed out. 


I don't think a flow has failed if a proper Run After Action has timed out parrallel branch properly executes. 


Is this a bug?

Community Support
Community Support

Hi @MWilliams86,


I think the Run After is built for error handling, have you checked the following blog?

Error handling steps


Basically I think if the action (more action settings ) is not correctly performed within the time range, then it should be considered as fail.


If you have any concerns or better idea, then please consider submit it as a new idea.




Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Well I guess if the error is handled then it should not be marked as fail. I have a flow that sends and item to approval. I configured the approval settings timeout to PT6H to wait 6 hours until timeout. If no response is received from the user in those 6 hours then I would take the decision of reject it automatically using a "run after" Action. But it is marked as fail despite I want this as the desired behavior. I do this because I don't want the flow to be running there for days and days waiting for a response from the user.



I noticed that the action fails if the timeout >= 1 hour.  If you specify it as for example PT10M, then the action succeeds.  So for me, this is a bug.  


In my case the problem is solved (so no bug after all) Smiley Wink

I was using Do Until to perform the action. I overlooked the limits in do until, which are by default :

Count : 60

Timeout: PT1H

I changed this to

Count: 60

Timeout: P30D

No my flow works as expected.


@MWilliams86 @noearcmon @v-micsh-msft 


Certainly a design bug! The timeout was handled, so the flow should not fail. Failure of the flow should be considered based on the failure of a step in the flow, and not just the occurrence of timeout. 


Oddly though this behavior doesn't occur when a terminate command is used (which I ended up using as a workaround)



2021-06-18 12_59_23-Run History _ Power Automate and 6 more pages - Work - Microsoft​ Edge.png


2021-06-18 12_58_17-Run History _ Power Automate and 6 more pages - Work - Microsoft​ Edge.png

Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Top Kudoed Authors
Users online (1,484)