How to resolve No Actions failed, no dependent actions succeeded error in below case.

[Anonymous]

Hi,

I am facing a weird problem with Flow. The subject I posted must be relevant to many as they might have come across the same but I just could not find the solution so wanted to see if someone can help.

I have a list setup as below: 

As you can see I have a basic list setup which contains following fields: Title, Expiration Date (date column, internal SP name: ExpirationDate), Business owner (free text) and Days (free text).

Basically the flow I have setup sends an email reminder 15 days prior to the expiration date to certain email recipients. The email should only go out 15 days prior to the expiration and only if the Days column contain value: 15. So I am using below condition in flow to automate this:

@AND(equals(items('Apply_to_each')?['ExpirationDate'],
formatDateTime(addDays(utcNow(), 15), 'yyyy-MM-dd')),
contains(items('Apply_to_each')?['Days'], '15'))  

Below is the flow screenshot.

I

Now when I run the flow, as per the SharePoint list, emails should be going out for Title: Expiration test item (since it has Days value to set to 15) and it works perfectly fine. I do see emails coming over properly for Expiration test list item but the flow however shows 'Flow run failed: No actions failed, no dependent actions succeeded.' The flow does its job but shows that it failed and I can't find what's worng here. Is this because the flow only found one item from the list under Apply_to_each block?

After digging for some more time, I updated Days Column and set it to 15 for second list item: Expiration test 2. I then ran the flow again and this time I see, Flow ran successfully and I got email notifications for both the list items this time. 

Can someone give me explanation on why I am seeing this behavior or help me if I have to change anything in the flow or condition I am using within. Eventually at the end of two weeks or so, Microsoft Flow sends an email out that the flows failed these many times last week which could become really annoying for the end client.

Any help will be appreciated, thanks in advance.

[ScottShearer]

@Anonymous:

Can you post a screen shot of a run (run history) along with the error details from the panel on the right?

Scott

[Anonymous]

[ScottShearer]

@Anonymous:

This looks like it might be a data type conversion issue.  What type of column is Days?  A number?

Scott

[Anonymous]

Its a free text column.

[Anonymous]

Also like I mentioned in the question description, when I had updated Days column field and set it to 15 for second list item: Expiration test 2 then the flow was showing ran successfully and emails came over fine for both the list items. Below are the screenshots for the same. 

1. Expiration Test 2 item has Days value set to 15, see below. The flow was then run again.

if type conversion was the reason then I don't follow why the flow ran next time showed as successful.

[v-yuazh-msft]

Hi @Anonymous,

Your flow run failed because there is an item with null value in the "Days" column, so the expression items('Apply_to_each')?['Days']   would run failed get the value in the "Days" column in the second loop:

 

Please let me know if you learn your issue now.

Best regards,

Alice

[Anonymous]

Hi Alice,

Thanks for your help. I follow what you are saying but then what is the solution to fix this? I mean the list I am trying to setup here in production would have Days column blank for some of the list items. If it shows failing like this, it won't be ideal at all. I belive Microsoft also turns a flow off if it fails certain number of times.

Appreciate your help, thanks.

[Anonymous]

Alice,

I also have this list setup for my Company's internal use where only Expiration Date column is present and likewise some of the list items do not have an expiration date value set, I am seeing the same issue as the one I mentioned here: "No actions failed, no dependent actions succeeded."

[v-yuazh-msft]

Hi @Anonymous,

You could add a Condition to check if the Days is empty, the screenshot of the flow should as below:

Best regards,

Alice