An action failed. No dependent actions succeeded.

[nickspizza]

Hi,

I have a flow that gets rows from excel and checks for conditions against certain values that I get from variables.

I am receiving the error: "An action failed. No dependent actions succeeded." even though the conditions are supposed to be met.

This is a row of data from the get rows function:

"InOut":"In","Employee":"Andrew Adams","TimeIn":"11:54:11","TimestampOut":"","KEY":"300","TimeOut":"","Duration":"","EmployeeName":"Andrew Adams","CheckOutAddress":"","Number of clock in addresses equal to clock out addresses":"0","email":"andrew@perx.co.za","Column1":"2022-10-19"},

These are the outputs by the variables: "Andrew Adams" and "2022-10-19" and the other condition is "In"

I don't understand why this keeps failing

[Sundeep_Malik]

Hey @nickspizza 

Check if data types are matching. Sometimes data types don't match and it gives such types of errors.

Also try using 

'In' 

Or 

"In"

Instead of In. 

Use composes to check, if the data types are similar or not or the data you are getting is correct or not. Use the composes before the condition.

[CraigStewart]

Are your variables dynamic or hard coded?
Duplicating this flow based on the information you've provided, it works, but I've made assumptions on the variables.

You could add some compose actions to the flow after the variables in order to double check the output

It also might not be the condition in the apply to each that's causing the issue even though that's where you see the error, if the conditions weren't met they would be going down the No route - what is happening in your Yes and No section of the condition?

If you open up the apply to each in the run history it should hopefully show where your failure is occuring.

[nickspizza]

When you say "apply to each's run history" do you mean this? The output just says that the expression result is "false"

Sometimes the flow runs but says that no conditions were met like this one a couple of minutes ago:

All the variables that are used in the condition are hard coded, I just used the variables to see the results of the values. I just ran the variable outputs through compose actions, not sure what to do with them inside the compose action though. Same result.

[nickspizza]

I made a copy of the excel file and tried to use just one condition and it gave me the same error gives me the same error if someone is willing to have a look:

Book3.xlsx

[nickspizza]

Can you try using this data for the flow that you tested: Book3.xlsx

[CraigStewart · Accepted solution]

I think you're reading your flow results wrong when you are looking at the screen that shows you 'false'

Here you should have a number of screens to rotate through - one for each line of your file.

It's possible you're only see 256 rows - which would likely give you the false - especially if you're looking for Andrew Adams who doesn't appear until row 297.

You'll see 296 "false" and then his "true" on 297

That is also why you'll be finding conditions not met, you'll need to enable pagination and set a number limit on the List rows present in a table action by clicking the 3 dots then settings

I've just run the flow with and without pagination and threshold set - WITH give the positive result above.

WITHOUT gives me the first screen.

Your error you've posted refers to the Update a row 3 action - which I assume is supposed to be using the output from your conditions , but as nothing met your conditions there is nothing to update, which is why you're likely getting the error.

Switch pagination and the threshold on and I think your problems will dissappear.

You'll likely want to move the update row action into your yes condition, as I assume that is what will drive it, so if the condition is met you update the row? Otherwise it will try to update rows without having anything data to do so - you'd also need it there should there be multiple rows being updated.

[nickspizza]

I needed to move all the actions that followed, into the condition loop as there were some conditions that had more than one true result and I guess the flow didn't know which one to assign the variable too. My bad. I forgot about the pagination in the test flow, but I had it turned on in the original flow. Thank you!