Power Automate · Cloud flows: action errors
500 Internal Server Error
Short answer
A 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.
VerifiedLast verified
01Error text
500 Internal Server Error02Likely causes
- The target service is experiencing issues.
03How to fix it
- Wait 15-30 minutes and retry.
- If it persists, check the Microsoft 365 Service Health dashboard or the non-Microsoft service's status page.
04Official documentation
→Related errors
- 502 Bad GatewayA 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.
- 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.
- 429 Too Many RequestsA 429 on a Power Automate action means you hit the API rate limit for that connector. Add a Delay action before the failing action, or enable a retry policy with exponential backoff in the action settings.
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