Answered

ActionFailed. An action failed. No dependent actions succeeded.

(4) Share

Report

Posted on by AlanHamaoui

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.PNG Approval Flow.PNG

Categories:

General topics

I have the same question (0)

All responses (15)

Answers (1)

Sort by

MarkStokes 561 on at

Like
a
(0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
AlanHamaoui 27 on at

Like
a
(3)

Report
Copy link

Link copied!

@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!Solution

Was this reply helpful? Yes No
Verified answer

AlanHamaoui 27 on at

Like
a
(4)

Report
Copy link

Link copied!

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).

Was this reply helpful? Yes No
MarkStokes 561 on at

Like
a
(1)

Report
Copy link

Link copied!

Awesome.

Good stuff.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!

I experience the similar issue 😞 what should be filled in "inputs" under "Compose"? also attached my flow below for reference.

Was this reply helpful? Yes No
tbrewer 7 on at

Like
a
(1)

Report
Copy link

Link copied!

I would like to know as well!

Was this reply helpful? Yes No
Eyfa 54 on at

Like
a
(1)

Report
Copy link

Link copied!

what is the input for compose action?

Was this reply helpful? Yes No
keensm60 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Not sure if this is what you are looking for but I added the 'Compose' action, right clicked on the elipsis and selected 'configure run after'.

Was this reply helpful? Yes No
Eyfa 54 on at

Like
a
(4)

Report
Copy link

Link copied!

I meant, what to put as compose input?

Was this reply helpful? Yes No
mvaladez 112 on at

Like
a
(1)

Report
Copy link

Link copied!

I came across this same issue and would like to know what to put into the compose condition

Was this reply helpful? Yes No