Flow trigger for when a new entry is added to the flow run history log

[DLeggett]

Please be kind, I am new to power automate and have grandioso ideas.

So I created a fairly lengthy work flow.  I have built-in error handling for specified conditions.  However, during my last test run, the flow failed while reading data from the source file into a variable.  In theory, I would need to have a "trigger Email upon failure" for EVERY action of the flow.  This obviously is NOT realistic.  So my thought is, is there a way to trigger a 2nd flow when a new entry is made to the 1st flow's log history?  I then could check the status of each new entry and if it is a Failure THEN trigger a generic flow failed email.  Thoughts?

[creativeopinion]

@DLeggett For each action that you want to log a failure for you will adjust the Configure run after setting. This setting allows you to specify the conditions under which an action should run based on the outcome of a previous action. 

You can add a parallel branch and insert an action that you'd like to run if the flow has failed.

However, best practice would be to adjust your flow to handle the errors accordingly. Sometimes if you adjust the logic of your flow and/or add some expressions—you can avoid the errors all together.

You may be interested in these YT Tutorials: 

5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows

In this Power Automate tutorial, I explore 5 frequently asked questions that pop up when troubleshooting a flow. If you’d like to to level up your Power Automate flow skills and learn how to troubleshoot your Power Automate flow—this tutorial is for you!

IN THIS VIDEO:

✅ How to troubleshoot a false Condition action result

✅ How to get dynamic content when it isn’t selectable from the list of dynamic content

✅ How to troubleshoot an Apply to Each action that isn’t looping through

✅ How to troubleshoot a skipped Apply to Each action

✅ How to troubleshoot a Filter Query

✅ How to use a SharePoint yes/no column in a Filter Query

✅ How to use Compose actions to troubleshoot a Power Automate flow

✅ How to troubleshoot multiple emails being sent

✅ How to troubleshoot multiple Teams messages being sent

-----

7 Functions You Need to Know | ⚡️Expression Essentials: Part 1⚡️

In this section, I'll cover how to get dynamic content with an expression when the dynamic content you need isn't listed in the dynamic content menu.

In the full tutorial I cover 7 functions you need to know when getting started with expressions.

1️⃣ empty()

2️⃣ coalesce()

3️⃣ equals()

4️⃣ if()

5️⃣ concat()

6️⃣ length()

7️⃣ split()

I cover how to use these functions in expressions and I’ll also cover common mistakes when it comes to writing expressions and show you a few tips and tricks along the way.

As a beginner or even an intermediate flow builder—expressions can seem a bit complex at first, I’m going to try to simplify it for you. If you want to level up your flows by writing expressions—keep watching!

IN THIS VIDEO:

✅ What is an Expression?

✅ What is a Function?

✅ What Does Wrapping a Function Mean?

✅ How Do I Insert an Expression?

✅ How to Use a Compose action

✅ How to Navigate the Expression Builder with Arrow Keys

✅ How to use the Expression Tooltip

✅ Common Mistakes When Writing Expressions

✅ How to differentiate a null from an empty string

✅ How to Get Dynamic Content When it’s Not Listed

✅ How to Use a Get Item Action to Verify Dynamic Content Output

✅ How to Convert Strings to Lower Case

✅ How to Troubleshoot the if() Function

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response!

👉 Level up your Power Automate skills by checking out my tutorials on YouTube
👉 Tips and Tricks on TikTok and Instagram

[DLeggett]

 Thanks for the tutorials.  So I do have significant error handling for errors I can predict.  However, there are about a dozen times that I parse data from a string array element, and if that data is junk, for whatever reason ,I figured adding an error handling to each of those steps would be time-consuming and slow the flow down.  In addition, I am unclear on what things trigger an API call that goes against the limit of our license.

I can add the additional parallel error handling, but is there no way to access the run history log for statuses?  That to me would be a better route.