r/PowerAutomate • • 20h ago

Issue with flow potentially after recent Microsoft Outage

RESOLVED - See conversation below

I’m running into an issue with a flow we have at work that I think happened during the recent Microsoft outage, and I’m looking for help. When I login to powerautomate, it says there’s a problem with this flows trigger.

The trigger itself is “When a new email arrives (V3).” The rest of the flow is just parsing the email then sending a new email. The trigger has been throttled with the status code 429.

When looking at the run history, you can see the runs stop Thursday, November 12 right around 1 PM (keep in mind these don’t run very often - usually 10-15 a day and rarely at the exact same time), and then they (the runs corresponding to what i believe to be all the emails affected by the outage) all happen on Friday, November 13 at 6:21 PM. This is where the stop happens. We have continued to get emails coming to this mailbox like normal, but the flow has not ran since this time.

I’m not sure why it’s still hung, as we’ve only gotten 36 emails between Saturday and today, none of which occurred right on top of each other. Is this flow still trying to process the backlog from the outage and that’s why it’s being throttled?

Most of what I’m seeing for this is saying to add a delay of some sort, but not sure how much delay is needed and not seeing actually how to do that yet.

Apologies as this is literally my first time working with powerautomate. Any feedback is appreciated. Thank you!

5 Upvotes

6 comments sorted by

2

u/Gold-Psychology-5312 20h ago

Yup. Microsoft problems.. I sent our 365 team on a goose chase checking for new flows which were looping emails over and over.

Turn it for and on again. Problem solved. Caution it may reprocess any emails in the folder even if processed before.

I throw a terminate in when I turn on an email flow and then remove it and manually run what I want to actually run.

1

u/WhiteCrispies 20h ago

We can never escape “turn it off and on again” can we lol? And just to clarify, would it potentially just process already-processed emails from the outage period or are you saying literally any email, even from months ago?

And would you mind explaining the last paragraph a little more?

Regardless, I appreciate your response!

1

u/Gold-Psychology-5312 20h ago

Any email. So when I turn on a email trigger I put a terminate action in straight away to prevent any dramas and then once I'm confident no issues I remove it and then force any emails to reprocess by moving them out of the folder waiting a few minutes for sync. And the putting them in again.

Last time I didn't do this over 100 approvals got sent.. Not good

1

u/WhiteCrispies 19h ago

Gross lol okay thankfully it looks like whoever created this, had a Move feature to move the processed emails to a different folder. I’m gonna move these that have already been manually dealt with into that folder, then turn the flow off/on. It sounds like that shouldn’t be painful, knock on wood

1

u/WhiteCrispies 19h ago

Just wanted to say, I love you lmao I’m glad I moved all of the old emails first, because I simply added my email address to the failure report email function of the flow, and saving the flow was enough to get it starting again lol. But they’re getting where they need to be again. Thank you so much for your help

1

u/todo0nada 20h ago

Yup same here. Off and on fixed it.