Flow disabled by power automate

[ReneRovekamp]

Within Teams I have made 20 private channels. All members can acces the general part of this teams site and depending on their role they can acces one other channel. All channels have different members, depending on their role. Several documents are for more then one role. But no document is to be accessed by all roles. We add members to Teams and one channel to secure acces.  

Channel 00. contains a library with all documents. Only the document owners can acces. Every document has an owner (column person picker) and a channel (column multiple choice channel 01. up to channel 20.) A document can only have one owner and several channels as properties. 

Every night a flow runs. This way, documents can be managed (updated) from one library. It collects all documents from library 00. 

A condition checks the channel column. All documents containing 02. will be copied from library 00. to library 02. 

Then the document properties from the copied document is changed. The document owner from library 00. is put into library 02. 

For every channel I set up a similar flow. 

The flows work fine as they do what I wanted them to do, but...

When I check the run history, every run fails. I ignored it, because documents and properties were ok. 

But now Power automate, turns of my flows because every run fails. What can I do? 

[ReneRovekamp]

This is what the flow looks like

[Pstork1]

What is the error message you get in the flow run?

[ReneRovekamp]

It says: An action has failed. No dependent actions were successful.

And that's the thing I don't understand. The actions I needed were performed. 

[v-alzhan-msft]

Hi @ReneRovekamp ,

The message "An action has failed. No dependent actions were successful." means the condition has run into the if no branch, the actions inside the if yes branch would run, however the flow has run successfully.

You could check from all the loops for the Apply to each, and there may have loop that Condition has run into the if yes branch.

Best Regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ReneRovekamp]

Hi @v-alzhan-msft 

Even in the YES branch it states the same message, but it has performed the actions correctly though. So I don't understand the message there. 

[Pstork1]

The problem is the second SharePoint action on the YES side of the condition.  Take a look at the specific error message for that step. That's the action that is failing and causing all the other error messages above it.

[ReneRovekamp]

Hi @Pstork1 

There It states the same message. But in the  output box it states 404 message: Could not find list item.

But, all actions have been performed. 

[Pstork1]

If it couldn't find the list item then that action wasn't performed and that is why the flow is failing.  You need to review that step in the previous runs and figure out why its not finding the item.

[ReneRovekamp · Accepted solution]

It took me a while, but I have found the problem. In the second action, I had the flow alter the file properties in library 2. In that action I referred to the ID of the file in library 1.

Because the properties from the file in library 1 was already copied to library 2 in action 1, the flow did what I needed it to do. 
Action 2 was redundant. I removed action 2 and it is now working without a problem. 

So thanks peeps, for pointing me into the right direction.

@Pstork1 @v-alzhan-msft