Power Automate · Cloud flows: action errors
429 Too Many Requests
Short answer
A 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.
VerifiedLast verified
01Error text
429 Too Many Requests02Likely causes
- You hit the API rate limit for this connector.
03How to fix it
- Add a Delay action before the failing action.
- Or enable a retry policy with exponential backoff in the action's settings.
- For flows that process many items, add a delay inside Apply to Each.
04Official documentation
→Related errors
- FlowRunQuotaExceededFlowRunQuotaExceeded in a Power Automate cloud flow: The flow or tenant exceeded its daily action execution limit. The most likely fix is to optimize action count, upgrade license.
- 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.
- 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.
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