Submitted on01-18-201912:17 AMSubmitted byAnonymouson01-18-201912:17 AM
Hi fellow Flow enthusiasts, TL;DR: Make error-codes from the Terminate-action visible in the run history of Flow. Please UPVOTE this idea if you find it useful und would like to see this in the future. Additional improvements can be stated in the comment section We all have been there. You have X amount of flow runs, all succeeded but only 1 of them is the Flow which you are searching for. With the "Terminate"-action we finally can manually let the unimportant Flows fail or cancel instead of marking the exceptions as succeded. This is already a step in the right direction. Also they give u the opportunity to set custom error-codes and messages if we let the flow fail manually. If this error-code (and possibly even the message) would be dislayed and it could be filtered upon that property this would make troubleshooting flows way easier. There could possibly also a code be used in the cancelled runs.
... View more
Hey guys, I used workaround described here - https://flow.microsoft.com/en-us/blog/error-handling/ 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. P
... View more