cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Franklin76
Frequent Visitor

Parent Flow of Nested Child Flows Not Getting Failure Notification

I have some Nested Parent-Child Flows within a Solution, that when a child Fails, it doesn't report back to the original parent.  The parent eventually fails, with a message that "The server did not receive a response from an upstream server".  This takes any where from 10-50 minutes for the parent to fail.  How can I get the Parent of the Nested Flows to fail in a timely manner?

Ultimately, I am trying to get this setup, so that I can get an email message when there is a failure within the workflow, but I don't want a message for each child that fails and don't want a delay in that message like I am seeing.

For example:

Parent flow, calling Child 1, which in turn calls Child 2.  If Child 2 fails, then Child 1 will report the failure immediately, but then Child 1 never seemingly returns the failure to the Parent, which eventually times out.

Do I need to add a separate 'Respond to a PowerApp or Flow' control, configured as Run After Failure?  Thanks for any assistance with this.

1 ACCEPTED SOLUTION

Accepted Solutions
ManishJain
Solution Sage
Solution Sage

Hi @Franklin76 ,

 

In the child flow implement scopes acting as Try catch mechanism , so that whenever it fails it will send the output back to Parent. it it not out of box but you can implement your error codes and messages and decode in the parent flow.

 

These are some of urls to help you further : 

 

https://blogs.msmvps.com/windsor/2019/04/25/microsoft-flow-error-handling/

 

 

https://sharepains.com/2018/02/07/power-automate-try-catch-finally-flow/

 

 

Thanks

View solution in original post

1 REPLY 1
ManishJain
Solution Sage
Solution Sage

Hi @Franklin76 ,

 

In the child flow implement scopes acting as Try catch mechanism , so that whenever it fails it will send the output back to Parent. it it not out of box but you can implement your error codes and messages and decode in the parent flow.

 

These are some of urls to help you further : 

 

https://blogs.msmvps.com/windsor/2019/04/25/microsoft-flow-error-handling/

 

 

https://sharepains.com/2018/02/07/power-automate-try-catch-finally-flow/

 

 

Thanks

View solution in original post

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MSFTBizAppsLaunchEvent

Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Top Solution Authors
Users online (18,379)