Thanks for the suggestion on using a filter array within the catch scope. I have just finished minor changes to my try-catch error handling, with posting errors and links to what has failed into Teams. Now, I will be able to improve it a bit more.

@Untethered365

2 ай бұрын

Excellent! Here if anything comes up.

I already use the Try-Catch pattern in my flows. However, I got some ideas to further enhance and optimize my current concept. Thanks. Subscribed to your channel.

@SeanAstro

4 ай бұрын

Excellent thanks Markus!

cool video, thanks!

@Untethered365

5 ай бұрын

Thanks for watching!

@steven9423

4 ай бұрын

This video is great and gives me a ton of ideas for implementation with the power automations that we are already using. I noticed the .edu domain you were using and was wondering if this is a part of a training offering?

Thanks, I have struggled for a few months trying to find a way to know exactly which flow failed. You are the best. Subscribed to your channel. P/s: I am thinking about running flows via NodeJS API with app permission, do you think it's possible?

@SeanAstro

3 ай бұрын

Glad it helped. Node can do that but I'm curious why you would need to.

Helpful information !! Thanks for posting. By the way, what is that screen snipping software you have used? Looks cool to retain the clip on the screen and compare with details

@SeanAstro

4 ай бұрын

Flameshot 🎉

Thanks very intesting. But how do you manage your share with your DEV Team ? Do you share the solution, do you publish the solution in app catalog (preview) ?

@Untethered365

24 күн бұрын

Catalog is creative but overkill for small to medium teams. I'd have them import it as unmanaged solution into their environment.

Hey, correct me if i am wrong but if there are multiple flows pointing to the error handling flow (child) and they are running it a lot, wouldn't it hit an actions run limit in Power Automate at some point?

@SeanAstro

3 ай бұрын

You should make sure you're not overusing it, e.g. have it run once if multiple items in loop fail and not on every run.

Nice! Get the url of the flow It´s not working for flows in solutions. The name of the flow is different to the url ID.

@SeanAstro

3 ай бұрын

Interesting - I have Flows inside a solution and they're linking fine. In fact, I got an error an hour ago and when I clicked it, it went to the expected run.

the function in the description is kinda messed up cause of url

@SeanAstro

4 ай бұрын

KZread is weird with URLs in the description 😮 hence the formatting.

Can you please create a video with multiple loop and how would you handle the error when the inner more loop fails it doesn’t fail the entire flow, i have to force throw a error like div/0 then that fails all the parents so now the filter on failed doesn’t work meaning i get 4 failed records 😔😔

@Untethered365

2 ай бұрын

Good idea! If I get some time I'll get on it.

@aravindnaveena5750

Ай бұрын

@@Untethered365 awesome 🫡🫡

@Untethered365

Ай бұрын

Here is a good post on it: www.linkedin.com/feed/update/urn:li:activity:7203287561115426816?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7203287561115426816%2C7203288452228866048%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287203288452228866048%2Curn%3Ali%3Aactivity%3A7203287561115426816%29

@aravindnaveena5750

Ай бұрын

@@Untethered365 thanks a lot thats a really good article i am going to implement that in my flow 👏🏽👏🏽👏🏽