Showing results for 
Search instead for 
Did you mean: 

Do not set flow as failed when used parallel branch

Hey guys,


I used workaround described here - as error handling for getmanager when no manager is filled for user. But the problem is that Flow is still in state Failed even that this, so it seems that it crashed, but it worked fine.



So i suggest not to detect such flow run as failed, cause it finished fine in parallel branch. I beleive that the problem is that the second branch was triggered also and that produced failure.

This should be definitely changed.



Status: New
Not applicable

You can easily mark it as succeeded by using the terminate-action after the http-action.
I would also suggest to use the Try-Catch-Pattern for error-handling.

As you seem to be interested in error-handling, please give me a upvote on following uservoice, thank you!

Kind Regards,
Leander S