Showing results for 
Search instead for 
Did you mean: 
Advocate II
Advocate II

ActionFailed. An action failed. No dependent actions succeeded - Error while Flow run

Hi All,


I have a flow that used to work without problem until few days ago, recently, some runs are presenting the "ActionFailed. An action failed. No dependent actions succeeded".


I noticed that these problems were related with Case or Switches. I have rebuilt the Flow and the problem persists. The error has no furhter details, so it makes even worse to troubleshoot. Any idea?



Community Support
Community Support

Hi @AllanMartins,


Thanks for reporting this.

Would it be available for you to share your flow configuration?

I will try to make some tests.


Make sure all the connections are in good condition, navigate to the connections page to see if there are any related connections need to update the credentials.





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

Is there any "easy" way to share the flow with you?


I thought about taking a screenshot, but the flow is just too big, it is too complicated to get in a screen? Is there anyway I can export it?


I went thru all the connection, and everything seems ok, the Flow itself works, but sometimes it simply fails... It started only about 2-3 weeks ago, before that, everything was just great....



There you go. That is one of the cases where sometimes works with no problems, other times simply fails

So, I created the flow from the scratch (with a different account) and also created all the connections from the scratch. It worked fine for a day, until I had another problem (like the previous one):




That Item that needs to be updated is ok, the ID does match, and it is all ok. Any idea?

Frequent Visitor

Has anyone figured out a solution?  I am getting the same error when using switch case.  after the flow runs, the expression result is one I am expecting, but the error does not allow the flow to continue.

Hi @mjmmet - after an update to the Flow Interface, I was able to identify the actual problem, for my case, it was related to the Token Validation, more information, details and the actual status for this problem are avaliable on this thread:



Helpful resources

Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (6,089)