Power Automate · Cloud flows: action errors
502 Bad Gateway
Short answer
A 502 on a Power Automate action means the connection between Power Automate and the target service failed. It is usually transient, so enable retry on the action and check network or firewall settings if it keeps happening.
VerifiedLast verified
01Error text
502 Bad Gateway02Likely causes
- The connection between Power Automate and the target service failed.
03How to fix it
- Enable retry on the action. The error is usually transient.
- If it happens consistently, check network and firewall settings, especially for on-premises gateways.
04Official documentation
→Related errors
- 500 Internal Server ErrorA 500 on a Power Automate action means the target service is experiencing issues. Wait 15 to 30 minutes and retry, and check the service health page if it persists.
- ActionFailedActionFailed in a Power Automate cloud flow: An action returned a failure status. This is a generic wrapper. The actual error details are in the action's output body. The most likely fix is to check action outputs for API error.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs