Hi,
Today since 2h all our flows started to fail with Bad Gateway error.
The Fail is always on Outlook related step (Get email / Move email / Send email from shared mailbox).
Is that a global issue? Nothing was changed on our side and these flows were running well for several months.
Are others experiencing similar issues or have some advice?
Thanks a lot
Thanks for the response. I'm brand new to PA and I'm still trying to find my way around the platform. I did find the post-incident report and it shows that it was an issue that was just on that day. My issue must be different, so I'll start a support ticket.
Thank you!
Hi,
For me everything started to work again on the same day (21.06.2022) later on when MS progressed on solving incident EX394347 that was the root cause of the Bad Gateway issue on our PA steps linked to Outlook. Since this time everything is running smoothly.
Same problem here. I set-up a new PA on 7/08 and I've gotten two fails so far with the Bad Gateway error. This original message was 3 weeks ago, but the issue is still happening.
Has anyone else had this error clear up for them yet?
Hi Guys. Same here. All our business flows are down. We are pushing everything manually. Hopefully posting to get any resolution. Thank you.
Looks like MS are aware and working on a fix as per the tweet from Dean's post
Thanks for info!
Do you know what could be our next steps to get it to someones attention at Microsoft?
It is the first time it happens to me but some of our significant business processes are relying on PA Flows.
@RedReno:I have also same problems asking me to sign in constantly.
Looks like Microsoft are aware of the issue and working on it.
Came here to post the exact same issue. As of 8am this morning, any flow with an Outlook step fails due to bad gateway/invalid connection. I can click on the connection and it asks me to sign in again, which I do, but then moments later it resets back to the same issue.
Seems to be a global issue. We are experiencing multiple systems failing including Power Automate.
I'm also getting that exact error on some of our Outlook Triggers/Actions
Screenshot for reference