Hi,
Sorry if this has been answered but I've searched extensively and not been able to resolve. I have a flow which is intended to delete superfluous junk mail that has keywords in the Subject or From fields without frequently editing Outlook rules. The flow steps through a list of keywords in a .txt file on Dropbox and moves the message to Deleted folder if one these words is found. The flow runs and produces the intended result but, most of the time, I get a failed run with error "An action failed. No dependent actions succeeded." I checked inputs and outputs and Message ID appears to be the same. Any idea why or how to resolve? [You can disregard the fact that I have no idea how get "Do Until" to work despite many tries.]
Solved! Go to Solution.
My bad, sorry. Place a single space in Value.
Hi, Just bubbling this up - any ideas? Thx!
Could you show the error message itself?
Hi Victor,
Here's a screenshot from a "failed" run. Thx!
Try to delete instead of moving to "Deleted items" folder.
Thanks, I think I've tried this in the past and found that using Delete Email action results in permanent deletion, does it not? I'd like to have a failsafe in case I need to find or recover a deleted message.
Understood. It seems you have to fix "Do until" then.
Recreated the flow without the whole "Do Until" loop. Still works like a charm and throws an error every time on "Action 'Move_email_2' failed".
Make sure that action 'Move_email_2' is executed only once for each message.
That takes me back to the version with the "Do Until" loop, which is illustrated above. Anyone have specific suggestions for how to get this loop to operate correctly?
Show your flow without "Do until".
Thanks, here it is.
Dirty fix: Place the action "Terminate" with the status "Succeeded" after move.
Clean fix: Check if the message exists before moving. If exists then move.
Hi Victor. Tried the "dirty fix" but you apparently can't put a Terminate control inside of an Apply to Each loop (you get error message: "The operation 'terminate' cannot be used inside a for each"). So I attempted the "clean fix" by inserting another condition before the Move action. I used Message ID to verify that the message exists but the flow still shows as a fail 1 out of every 6-7 runs even though it is working
Would anyone have perhaps more explicit detailed advice on how to fix? Thanks!!.
Hi @BRubble,
sorry I forgot you are moving email inside a for each.
Well, place an empty "Set variable" action after "move email". Click on three dots of "Set variable" action.
Select "Configure Run After" and mark all 4 checkboxes.
Set Variable requires a name (of a variable that has been initialized) and it requires a value, i.e. can't be empty.
Semi-correct. Initialize a string variable and name it. Then in the "Set variable" action you can leave a value empty.
I must be doing something wrong!
My bad, sorry. Place a single space in Value.
Thanks again, Victor!! So far, this appears to have done the trick. If I understand correctly, what I've done with this suggested fix is suppress reported failures by using the "run after" step to keep the flow going after Move Email is executed, right? Wonder why it fails in the first place.
User | Count |
---|---|
88 | |
39 | |
23 | |
20 | |
16 |
User | Count |
---|---|
128 | |
47 | |
46 | |
27 | |
25 |