Need to write a condition for search for users, where is the email is valid one set of steps follow, and if the email is not valid another set of steps follows

[glavanco]

Need to write a condition for search for users, where is the email is valid one set of steps follow, and if the email is not valid another set of steps follows - but my flow is stopping at the Search for Users step because some of the email address it is finding are not valid. 

Not sure if it's how i'm writing my condition?

[Expiscornovus]

Hi @glavanco,

You can configure the run after setting in the Condition action and enable the has failed status as well.

Below is an example (click on gif to see in high resolution)

After that you can check the outputs, like the length expression in the condition. Like you are already doing.

[glavanco]

Thank you!! In all of my searches - this never came up as an option!! 

Now i'm running into another problem... My condition isn't doing what I was hoping it would.

The goal is for the search to go through an array, and determine which email addresses are valid and which are not. 
If they are valid (If Yes) they should continue on with my "Yes" Flow to send a particular email to the users email address. 
If they are invalid email addresses (If No), it should continue on with my "No" flow, and send an email back to me, letting me know the user email address is invalid.

I'm not exactly sure which condition I should be using, not sure if length is the correct one (it was something I had found in another video...i've tried using a few different "Dynamic Content" options inside of the length expression, but they have all thrown back errors.  The one attached here is when using the "Value" from the output of Search for Users.  I also tried with the Output of my "compose email address array" 

[Expiscornovus]

Hi @glavanco,

I see you are searching for multiple users at once in the search for users (v2) action and you are getting an error in there, which is different that the no valid email address error. To avoid that from happening I would suggest to search for a single user per loop item by using the current item of the loop (one single email address).

Below would be my suggested setup

[glavanco]

So this ended up running through the entire flow, which is good...however, it skipped the "If No" (which has the intent of sending an email back to me because the email address that was searched is invalid)

I'm going to attach a few files from both the results view and the edit view of what is going on.

The "story" of this flow is that I have a sharepoint list where one of the columns is ADLEmailAddress
I need to have the flow check the email addresses inside the ADLEmailAddress column, and then strip it down to show one entry per email address. 

It needs to then check to see if those email addresses are valid or invalid in our company directory.

Send one set of emails to the valid ones (with further action items for them) and one set of emails back to me if the address is invalid, telling me what the address was.
The flow (at the end) sends ONE email with a table of the items listed under that particular ADLEmailAddress to the valid addresses, and send me one back telling me which ones were invalid so I can do further research into them.

[Expiscornovus]

Hi @glavanco,

Thanks for clarifying your requirements. In that case I would use two temporary arrays.

You can append the current item to either a Valid users or a Invalid users array. Outside the loop you can use those arrays in the body of your email.

Below is an example of that approach.

In this sample I am using a join function to return a comma separated string value of email addresses.

However, you could also use a Create HTML table actions outside the apply to each loop with the ValidUsersArray and InvalidUsersArray as input. 

Body of Send an Email (v2) action in HTML view

<p><br></p>Valid Users: @{join(variables('ValidUsersArray'), ',')}<br>Invalid Users: @{join(variables('InvalidUsersArray'), ',')}