Flow "Successful" but not really..

[rtaylor1stComm]

Hi Power Automate World, 

Another Newb question from me. I'm testing a simple flow I created that renders a successful status at each run, but the final step isn't being completed because the conditions are all coming back "false" but there's one I've purposely made "true" for testing. I think the hangup is somewhere in the condition I have set up, and I can't tell if the fix lies in PA or within the Excel Doc I'm using. 

Here's my flow. I've tried both "Apply to Each" and/or "For Each" and neither yield the result I need. 

My condition is set to look for Days Left to be equal to 160 and if "True" send an email to the user (me, in this test case) notifying the user that their license is due soon.

The example below is a shot of the row I have set up in my table to test. You can see "Days Left" is 160. This is the 29th row of my table. 

However, when the test runs, I get a message over at the "Send Email" step that says ActionBranchingCondition is not satisfied, and when I go through each row entry, I come to row 29 and see that the came back "false" instead of true, even though Days Left does equal 160

I've run the mill of ways to edit, but again, I'm not sure if this actual flow or the way I have "160" formatted in the Excel table. I have it as a Number format because I have a formula running that calculates amount of days from today's date to the actual due date. 

Any advice would be appreciated as I learn this program. 

[SudeepGhatakNZ]

I can take a look on a Teams call. Are you available now?

[rtaylor1stComm]

Thank you for your suggestion; however, being that I'm using my work network and server, I won't be able to take you up on that Teams call for security reasons. 

thank you, 

[creativeopinion]

@rtaylor1stComm Instead of using an Apply to Each (aka For Each) and Condition action to loop through each row in your Excel table to see which rows meet your criteria. It's a lot more efficient to use a Filter Array action or a Filter Query in the List Rows Present in a table action.

If using a Filter Query in the List Rows Present in a table action, you need to ensure your column header doesn't have any spaces.

Note: The List rows present in a table action returns up to 256 rows by default. In order to get all rows, you will need to toggle on pagination and set a threshold. 

Whenever I use a Filter Query in a List Rows Present in a Table action, I always like to return the count of items returned in a Compose action. This is helpful when building a flow and can also be used to troubleshoot your flow.

Insert a Compose action. Add an Expression. Use the length() function.

Select the Dynamic content tab and insert the body dynamic content from the Filter Array action into the length() function.

Add a Condition action to your flow. If items have returned (aka there is number stored in the Compose action—that is not equal to 0), add the rest of your actions to the Yes branch. If not, do nothing.

For more flow troubleshooting tips—check out this YT Tutorial: 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

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

[rtaylor1stComm]

Thanks for this. I did try it, and got a little confused at "Add a condition" when  you said if items are returned (aka there's a number stored in your Compose action). I just built the flow almost verbatim how you suggested, using the length expression in the Compose action. So, I'm a little confused on what you mean by "number stored" there. 

[creativeopinion]

@rtaylor1stComm When you run a test, the Compose action will output a number. This number will indicate how many items have returned from whatever you've inserted into the length() function. In your case, it'll be the number of rows returned from the List Rows Present in a table action.

[rtaylor1stComm]

Thank you, 

The test keeps failing so I don't have a number generated; however, I have 31 rows on my excel list (at the time) I don't ever see it growing to be over 256 rows, so is the Pagination option necessary? 

Thanks for all your help. What's so frustrating is my original flow worked and sent out emails successfully at a time; however, I went in to edit the flow just to fix a date-formatting error within the email body of the last action, and it hasn't worked since. 

[creativeopinion]

@rtaylor1stComm can you please share a screenshot of your full flow in the Classic designer with all actions expanded (in edit mode)? Also, if you are switching between the new designer and classic designer I'd recommend sticking with the classic designer as the new designer is still buggy.  

If your excel table will never go over 256 rows, then toggling on pagination isn't necessary. 

[rtaylor1stComm]

So what I've done now, is start from scratch and test each action/step of the flow before adding anything else. My test number to find in the DaysLeft column of my excel table is 145. From the screenshots, you can see my Compose actions is in fact bringing back 145 from the 30th row of the table. 

Going from there, I add a Condition and it creates the For Each. I need to choose an output from the previous step. I only have the options you see in the next screenshot, so I select it. 

From there, my Condition window pops up and from the Dynamic Content list, I have the columns of my table and some other options to choose.

This is where it gets tricky! I've tried everything I thought would work at this step, however--all results come back "false" and therefore I'm not ready to add the next action. It's saying it's successful, because it didn't run into errors, but to not see the 145 as "true" is an error for me. 

[rtaylor1stComm]

I'll update my lastest reply with screenshots of the Classic Mode. I hadn't seen your request for this before posting. 

[rtaylor1stComm]

It doesn't like when I do the Filter Query. It fails and says 'BadRequest' any time I add it. It passes at least this first step when I don't have it. 

Flow in Edit Mode 

[creativeopinion]

@rtaylor1stComm I would stick with working in the Classic Designer as the New Designer is still buggy. I believe you have the length() expression set up incorrectly. Can you try again? Following these steps?

Select the Dynamic content tab and insert the body dynamic content from the Filter Array action into the length() function.

You can reference this section of my YT Tutorial to see a demo of this. Although this demo is returning the count of SP Items, you can apply to concept to the List Rows Present in a Table action. Insert the value dynamic content into the length() 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

[rtaylor1stComm]

I have the expression as 

length(outputs('List_rows_present_in_a_table')?['body/value']). This was generated after I set the cursor inside of the parentheses, then selected Dynamic Content/Value

[creativeopinion]

@rtaylor1stComm Is the Compose action still outputting an error or does it output a value?

[rtaylor1stComm]

the List Rows Action is still failing due to 'BadRequest'. This only happens when I have something the Filter Query. Here's a screenshot. Note: I've tried both putting quotations around 145, and not. In this screenshot the quotations are there, but either way causes a fail. 

[creativeopinion]

@rtaylor1stComm What type of data is stored in the DaysLeft column of your table? Also, confirming that DaysLeft matches the text of the column in your table. If so, then I would recommend creating a brand new flow and toggling off the New Designer before you start editing. Since you've already edited your flow in the New Designer, it may have caused some issues. Better to start fresh. 

[rtaylor1stComm]

So, I'm getting somewhere! Switching to the classic view and adding "" around the number 145 in my condition action finally rendered a true return. 

Now...there's this 😫

I received the email from the final action/step but now I have a date formatting issue! ayi yi yi. This is where it all went wonky before. I'd reached out to help about the formatting and was told to place this expression in my email body : 

addDays('1899-12-30',items('For_each')?['Expires'],'dd MMM yyyy'). 

However, even though the expression was accepted, It caused the flow to fail

When I use the Dynamic Content from my 'Expires' column from the Excel Table, the flow runs, but gives me that full number date format from the first screenshot above. Here's the data I have in that column. So close to the finish line! 

[creativeopinion]

@rtaylor1stComm As mentioned in my original post, it's a lot more efficient to filter out the items that you want to loop through using the filter query in the List Rows Present in a table action rather than looping through all rows and running a condition check as you have.

I'd recommend using a filter query as it'll make your flow more efficient. 

Refer to the YT Tutorial linked below for details on how to use the addDays() function.

How to Work with 📆 Dates in Power Automate | Example Scenarios and Tips & Tricks

Are you easily stumped when working with Dates in Power Automate? In this Power Automate tutorial, I’ll show you how to compose an expression that will return a future date, a past date, how to count the number of days between two dates, how to check for a birthdate and anniversary date as well as tips and tricks when working with dates in Power Automate.

I’ll cover some common use cases and concepts that can help you to build better Power Automate flows. Feel free to skip ahead using the timestamps listed below. I’ve also linked a few other tutorials that you might be interested in as well.

IN THIS VIDEO:

✅ 4 Date Functions You Need to Know

✅ How to use the Convert Time Zone Action

✅ How to Get a Future Date

✅ How to Get a Past Date

✅ How to Return SharePoint Items Due in a Number of Days

✅ How to Return SharePoint Items Due within a Date Range

✅ How to write a Filter Query for SharePoint Items Due in 30, 60 and 90 Days

✅ How to Calculate the Number of Days between Two Dates

✅ How to Check for a Birthdate and Anniversary Date

✅ How to work with Dates and Times in Excel

✅ How to use a Manual Trigger with Date Input

✅ How to Output Dynamic Text with an Expression

✅ How to Check if a Date Falls on a Weekend

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

[harshporecha]

Hi, Can you please try to convert the value to appropriate type like int. that may be creating issue in comparison. You can convert value using function int(). 

[rtaylor1stComm]

Thanks for this and I appreciate it; however, filter queries are not working for me and I'm kind of over trying that part, as I can't troubleshoot why my flows fail due to BadRequest when I use a filter query. But I will definitely take a look at the link regarding the addDays expression. 

thank you,