Great information. I was using the try catch scopes. This just takes it to the next level. I hadn't thought about the terminate step to mark it as a failure. I still feel Microsoft should have put more into the error handling. As every other syatem I had used in the past has this kind of handling built in.
@DamoBird3652 жыл бұрын
Cheers Phil. I could also imagine having a status in the list that is used to record the urgency of the error from flow and potentially then having a new flow that triggers on new item being created where status = urgent, so that you could include some form of secondary alert. Lots of potential ideas here. 👍
@jeromerancourt819 Жыл бұрын
Thanks for these explanations. Error handling is always forgot and it get hard to correct little bugs... I successfully put in place most of what you showed on this video and it helped me a lot. I already subscribed and liked your channel. What can I do for you ?
@DamoBird365 Жыл бұрын
Hey Jerome, happy to help. If you think of any video ideas feel free to reach out 👍
@mattiabergo7222 Жыл бұрын
Thank for this video, it is definitely the most rich on abour error handling! One question about a specific scenario I have: what about errors happening in actions inside If blocks or nested If blocks? every time I cannot dig into the final action error message throwing the error, because the 'Select' action of the Catch scope is getting only the first level of the error, therefore always saying 'An action failed. No dependent actions succeeded." That of course is not explanatory. I can send my screenshots if required in other ways.
@DamoBird365 Жыл бұрын
You would need to run the result() on nested actions that you want to get the error for. It can only return top level errors.
@chimanwokeocha33119 ай бұрын
hello, please is there a solution to make one flow which would add check every flow in the environment and add it to the list. because it is impossible now to add the catch and scope steps to old flows if they are 100s of flows in the environment. what ways can we monitor a flow if it fails one or multiple times and then be alerted
@DamoBird3659 ай бұрын
This preview feature is worth knowing about learn.microsoft.com/en-us/power-platform/admin/app-insights-cloud-flow
@baojiangwang86758 ай бұрын
But we can not find this preview feature in current live power automate environment , right ?@@DamoBird365
@syedgazanfar77957 ай бұрын
Amazing ❤
@400_Labs Жыл бұрын
So when I attempt to use the URL to see the flow run history, I'm getting an error 404 message. I thought maybe best the URL has "shared" in it because it is a shared flow, but even after modification, it still fails to take me to the right web page. Any ideas?
@DamoBird365 Жыл бұрын
Navigate to a real flow history page and copy the url from the browser. Compare your generated version with the actual URL and hopefully you’ll spot the difference. Please let me know how you get on.
@lordLofi72 жыл бұрын
Hello, gretings from Brazil. For some reason the error message always return "null", could you help me? I tried every possible way and the return is always the same.
@DamoBird3652 жыл бұрын
+Davi null would mean that your expression is not finding the final value. Could be a typo?