Power Automate errors
Common Microsoft Power Automate errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 29
- Components
- 14
- Verified
- 29
- Official docs
- learn.microsoft.com/en-us/power-automate
29 errors in 14 groups
Cloud flows: action errors3
- 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.
- 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.
- 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.
Cloud flows: action inputs1
Cloud flows: child flows1
Cloud flows: connection and authentication errors5
- ConnectionAuthorizationFailedConnectionAuthorizationFailed in a Power Automate cloud flow: The connection exists but its stored credentials are no longer valid. The most likely fix is to fix connection, re-authenticate.
- ConnectionNotConfiguredConnectionNotConfigured in a Power Automate cloud flow: An action requires a connection but none was selected. The most likely fix is to select or create a connection.
- Forbidden (403)Forbidden (403) in a Power Automate cloud flow: The authenticated user or app doesn't have permission to perform the requested operation. The most likely fix is to check DLP policies, permissions.
- InvalidConnectionInvalidConnection in a Power Automate cloud flow: A connection reference in the flow points to a connection that is broken, deleted, or expired. The most likely fix is to re-authenticate the connection.
- Unauthorized (401)Unauthorized (401) in a Power Automate cloud flow: The API rejected the request because the authentication token is invalid or expired. The most likely fix is to fix connection, rotate credentials.
Cloud flows: connections1
Cloud flows: connector and api errors3
- 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.
- BadRequest (400)BadRequest (400) in a Power Automate cloud flow: The connector API rejected the request because the input data is malformed or invalid. The most likely fix is to validate input data format.
- NotFound (404)NotFound (404) in a Power Automate cloud flow: The resource the action is trying to access doesn't exist. The most likely fix is to verify resource exists, update references.
Cloud flows: design-time errors4
- DuplicateActionNameDuplicateActionName in a Power Automate cloud flow: Two or more actions in the flow have the same internal name. The most likely fix is to rename one of the duplicate actions.
- FlowCheckerErrorFlowCheckerError in a Power Automate cloud flow: The flow checker found one or more validation issues that prevent saving. The most likely fix is to fill required fields, fix connections.
- InvalidTemplateInvalidTemplate in a Power Automate cloud flow: The flow definition contains a syntax error in an expression or action configuration. The most likely fix is to fix expression syntax.
- MissingRequiredPropertyMissingRequiredProperty in a Power Automate cloud flow: A required input field on an action or trigger is empty. The most likely fix is to fill in required fields.
Cloud flows: licensing errors1
Cloud flows: run duration1
Cloud flows: runtime expression errors2
- ContentConversionFailedContentConversionFailed in a Power Automate cloud flow: The flow couldn't convert data from one type to another between actions. The most likely fix is to use explicit type conversions.
- ExpressionEvaluationFailedExpressionEvaluationFailed in a Power Automate cloud flow: An expression failed to evaluate at runtime because the actual data didn't match what the expression expected. This error only occurs when the expression uses **dynamic values** (variables, trigger body, action outputs) that can't be checked at save time. The most likely fix is to add null checks, validate types.
Cloud flows: Scope1
Cloud flows: timeout and throttling errors4
- ActionTimedOutActionTimedOut in a Power Automate cloud flow: A single action exceeded its configured timeout and was canceled. The most likely fix is to increase timeout in action settings.
- 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.
- OperationTimedOutOperationTimedOut in a Power Automate cloud flow: A long-running operation (webhook wait, approval, HTTP polling) exceeded the maximum wait time. The most likely fix is to set explicit timeouts, use relay pattern.
- WorkflowRunActionRepetitionQuotaExceededWorkflowRunActionRepetitionQuotaExceeded in a Power Automate cloud flow: An Apply to Each loop exceeded the maximum number of iterations (default: 100,000 for premium, 5,000 for performance profiles). The most likely fix is to filter data before looping.
Cloud flows: trigger errors1
SharePoint connector1
More for Power Automate work:Open Power Automate jobs
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.