Looks like there's a false positive? I don't know how to get rid of it...

[JoshuaWalters]

This flow works completely, but it still raises an error on my apply to each loop saying "An action failed. No dependent actions succeeded." which is just plain wrong. Am I misunderstanding something here?

[JoshuaWalters]

I've even tried removing the variables and the compose (they're redundant right now) and it STILL shows an error even when I definitely receive an email with all the information in it that I was trying to retrieve from all the rows that met my conditions...

[creativeopinion]

@JoshuaWalters Can you share a screenshot of your flow in the Classic Designer (toggle off the New Designer) with all actions expanded.

This notice: An action failed. No dependent actions succeeded means that there aren't any items for the Apply to Each (aka For Each) action to loop through. I'm assuming you have a Filter Query in your List Rows Present in a Table action. 

The Filter Query in the List Rows Present in a table action only accepts a single condition. If you need to filter your rows with more than one condition, you'll need to use the Filter Array action. 

In the meantime, you might find these YT Tutorials helpful:

Are you using the Microsoft Power Automate Filter Array Action wrong?

In this video tutorial I’ll show you 3 practical ways to use the Filter Array action and how to use it properly.

1️⃣ Cross-Referencing Data

2️⃣ Filtering by Key

3️⃣ Substring Matching

Did you know that the Condition action has a limit of 10 conditions? Although it might look like the Filter Array action can only accept one condition—this is not true. By using the advanced mode you can enter multiple conditions into a Filter Array action with an expression.

IN THIS VIDEO:

✅ 3 Ways to Use the Filter Array Action

✅ How to use the Scope Action to Group Actions

✅ How to Check the Number of Items returned from a Filter Array Action

✅ How to Cross-Reference Data in Excel with a SharePoint List

✅ How the Filter Array Action Works

✅ How to Access the Dynamic Content from a Filter Array Action

✅ How to Filter Items by a Key

✅ How to Filter Items by Matching a Substring

✅ How to Use Multiple Conditions in a Filter Array Action

---

3 Mistakes YOU 🫵 are Making with the Apply to Each Action in your Microsoft Power Automate Flow

In this video tutorial I’ll go over how to avoid these common mistakes when using the Apply to Each action in a Power Automate flow:

1️⃣ Looping through a Single Item

2️⃣ Creating Unnecessary Nested Loops

3️⃣ Looping through an Unfiltered Array

At the end of the video I share a few helpful insights when it comes to using the Apply to Each action in your flow.

IN THIS VIDEO:

✅ How to avoid the Apply to Each action with a single item array

✅ How to use the item() function to access dynamic content in an array

✅ How to prevent unnecessary nested Apply to Each action loops

✅ How to use the Select action

✅ How to convert an array to a string with the Select action

✅How to use the Filter Query field

✅ How to count the number of items in an array

✅ How to use a condition control

✅ How to use the concurrency control

✅ How to set a top count

✅ How to use Compose actions for troubleshooting

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

[JoshuaWalters]

Thanks for your quick response, here it is:

I haven't changed anything in the advanced options of any of my nodes, so I'm not actually filtering anything; I'm looping through all rows and only actioning ones that meet my condition.

[JoshuaWalters · Accepted solution]

Never mind, I found out what the issue was but without @creativeopinion I wouldn't have found it. The error was much more verbose in the old designer view, and actually told me it was a formatting error because I accept both dates and the word "INDEFINITE" in one of my date columns. It was trying to format a non-datelike string into a date format... Basically, just don't use the garbage new design view.