I have a flow that I included a Move Email step. The flow triggers on a new email. It copies the attachment to a SharePoint folder. Then it moves the e-mail to a different folder. I have been getting failure notices saying that the Move failed. However, when I go to check my email inbox, the message has been moved. So, the Move email step actually does work but it throws a failure. Any ideas on why this is? I added a Delay (5sec) before this step to try to get past it, but that didn't work either. It doesn't fail every time either. It is hit and miss. A real pain when this flow is running 100+ times a day.
Solved! Go to Solution.
Sorry, I think you have missed the point.
There is a bug in Power Automate - the action "move" moves an email but shows a false error.
You ignore any errors but after moving you check if an email is really moved.
If it's not moved you generate the error yourself.
If it's moved, all is fine and you do nothing.
OK, I think I have found a change that eliminates the false errors.
Email comes into an account from multiple sites. I have a switch in the flow that determines which folder to save the attachment to based on which site it originated from. Inside the switch, I save the attachment off and move the e-mail. I eliminated the "Move Email" from inside each branch of the switch so I only have one "Move Email" after the switch. Since doing that, I have not had it throw any more false errors. Don't know why it would make a difference.
Hello @swarrenjr,
set "run after" to ignore this error.
Not really a solution I can use. If I ignore a failure, how would I know if it actually did fail? I can't give up notifications on failures.
Well, if you know that's a false error you can ignore it, right?
And to know if it actually did fail, check the absence/presence of the moved email after moving.
You seem to be missing the point. It is possible that it would fail with a real issue at some point in the future, correct? So, if I am ignoring errors, then I will miss a real error as well as the false errors. Again, ignoring the failure is not fixing the issue. Not a solution.
Sorry, I think you have missed the point.
There is a bug in Power Automate - the action "move" moves an email but shows a false error.
You ignore any errors but after moving you check if an email is really moved.
If it's not moved you generate the error yourself.
If it's moved, all is fine and you do nothing.
Wow. That answer is a lot different than the first one. This one actually makes sense.
Adding extra checking in the process will be painful but I could test it out and see if that works.
Hopefully Microsoft will resolve the Bug they have then in the move.
Yes, my bad - my first answer was too short. Shame on me!
OK, I think I have found a change that eliminates the false errors.
Email comes into an account from multiple sites. I have a switch in the flow that determines which folder to save the attachment to based on which site it originated from. Inside the switch, I save the attachment off and move the e-mail. I eliminated the "Move Email" from inside each branch of the switch so I only have one "Move Email" after the switch. Since doing that, I have not had it throw any more false errors. Don't know why it would make a difference.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
At the monthly call, connect with other leaders and find out how community makes your experience even better.
User | Count |
---|---|
5 | |
5 | |
3 | |
2 | |
2 |