cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
New Member

ActionFailed. An action failed. No dependent actions succeeded.

Hello,

 

I have a Flow that I created from scratch and am getting the error "ActionFailed. An action failed. No dependent actions succeeded.", however, the Flow executes exactly as it should, meaning, it does what it was programmed to do.

 

It seems that the error occurs whenever 'final approval' times out. I set 'final approval' to time out after 1 week and set the 'configure run after' for 'send approval request to leadership if final approval times out' to "has timed out".   

 

The 'configure run after' for 'final approval condition' is set to "is successful". 

 

However, whenever 'final approval' times out, the rest of the flow executes successfully but i get a 'flow failed error'. When reviewing the error, 'final approval condition' has a message that reads 'ActionConditionFailed'.

 

Any ideas how to fix this?

Pictures of flow attached. Approval Flow errors.PNGApproval Flow.PNG

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
New Member

Re: ActionFailed. An action failed. No dependent actions succeeded.

Solution:

Add a 'compose' action at the end that joins both branches together. Set the 'configure run after' for the 'compose' action to "is successful" and "is skipped" for both conditions (image attached). 

 

solution.PNG

View solution in original post

4 REPLIES 4
Highlighted
Skilled Sharer
Skilled Sharer

Re: ActionFailed. An action failed. No dependent actions succeeded.

Yes. This happens and its a bit frustrating.

 

It is really a false-positive as It has actually run correctly.  I "think" you can get aroudn this by putting an Action at the very end of your Flow. Just a simple Compose action or something like that. I am pretty sure in my own Flows that makes the Flow complete with a success.

 

- Mark

Highlighted
New Member

Re: ActionFailed. An action failed. No dependent actions succeeded.


@MarkStokes wrote:

Yes. This happens and its a bit frustrating.

 

It is really a false-positive as It has actually run correctly.  I "think" you can get aroudn this by putting an Action at the very end of your Flow. Just a simple Compose action or something like that. I am pretty sure in my own Flows that makes the Flow complete with a success.

 

- Mark


Mark,

You are exactly right, it is a false positive. I did a little digging before seeing your answer and you are partly right. Adding a 'compose' action at the end that joins both branches together does work, however, you need to set the 'configure run after' for the 'compose' action to "is successful" and "is skipped" for both conditions (image attached). 

 

Thanks for the help!SolutionSolution

Highlighted
New Member

Re: ActionFailed. An action failed. No dependent actions succeeded.

Solution:

Add a 'compose' action at the end that joins both branches together. Set the 'configure run after' for the 'compose' action to "is successful" and "is skipped" for both conditions (image attached). 

 

solution.PNG

View solution in original post

Highlighted
Skilled Sharer
Skilled Sharer

Re: ActionFailed. An action failed. No dependent actions succeeded.

Awesome.

Good stuff.

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Upcoming Events

Experience what’s next for Power Automate

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Users online (6,768)