Power Platform Community Forum Thread Details

all of a sudden my flow isnt working and I see a bad gateway error.... is that just a broken connection ?

Categories:

Hi there,

A sudden "Bad Gateway" (HTTP 502) almost always points to a transient connector/gateway issue rather than something wrong with your flow logic. Here's how to triage it:

1. Check the connection used by the failing action

Open the flow → Connections and confirm the connection shows Connected (not "Fix connection").
If you use an on-premises data gateway, confirm its status is Online in the Power Platform admin center.

2. Repair / re-authenticate

Edit the failing action → click the connection → Add new connection and sign in again. Token expiry is a common 502 cause.

3. Inspect the run history

Open the failed run, expand the failing action, and copy the full error JSON. The status and x-ms-failure-cause tell you whether it's ClientConnectionError (transient) vs. a service-side fault. See Fix a flow that has failed.

4. Add resiliency

Configure retry policy on the action (exponential, 4 retries is a good baseline) so transient 5xx errors auto-recover.

5. If the gateway itself is the cause

Follow the on-premises data gateway troubleshooting steps — restart the gateway service, check connectivity to *.servicebus.windows.net, and confirm the gateway version is current.

If it returns intermittently and a retry policy resolves it, it's a transient service hiccup. If it's persistent on one connector only, the connection needs to be recreated.

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs