Power Automate Error Codes Reference

Quick Lookup: HTTP Status Codes

Code	Name	What it usually means	Try this first
401	Unauthorized	Authentication failed. Credentials missing, expired, or invalid.	Re-authenticate the connection (Data → Connections). Check the run-as user still has access. Verify OAuth tokens haven't expired.
403	Forbidden	Authenticated but not allowed. You're logged in but don't have permission for this action.	Check permissions on the target resource (SharePoint site, list, Dataverse table, etc.). Verify licensing (Premium actions need Premium).
429	Too Many Requests	Rate limit or throttling. You're hitting the connector too fast.	Add delays between actions. Reduce For each parallelism. Use retry policy with exponential backoff. Stagger scheduled flows.
400	Bad Request	Invalid input. The request format or parameters are wrong.	Check inputs to the failed action. Verify property names, data types, required fields. Look at the error body for details.
404	Not Found	The resource doesn't exist or the path/ID is wrong.	Verify URLs, list names, item IDs. Check if the resource was moved, renamed, or deleted. Dynamic content may point to the wrong property.
500	Internal Server Error	Something broke on the service side. Often temporary.	Retry the run. Check Power Platform status. If it recurs, open a support ticket.
502	Bad Gateway	Gateway or proxy error. Upstream service didn't respond correctly.	Usually temporary. Retry. Add retry policy. If persistent, the external API or connector may be unstable.
503	Service Unavailable	Service overloaded or down for maintenance.	Wait and retry. Check service health. Add retry with backoff.
504	Gateway Timeout	The upstream service took too long to respond.	Action may be timing out. Split large operations. Increase timeout if the connector supports it. Retry.

Common Power Automate–Specific Errors

Error	What it usually means	Try this first
InvalidTemplate	Flow definition has a syntax or schema error.	Check expressions for typos. Verify dynamic content references. Re-save the flow. May require editing in Power Automate (not Logic Apps) if migrated.
Unauthorized / AccessDenied	Same family as 401/403. Connection or permission issue.	Re-create or refresh the connection. Verify user has access to the connector and target resource.
BadRequest / InvalidRequest	Same family as 400. Inputs don't match what the connector expects.	Inspect the failed action's inputs. Check for null, wrong type, missing required field. Validate against connector docs.
Throttled / TooManyRequests	Same as 429. Connector rate limit hit.	Add delays, reduce concurrency, use retries. See connector limits.
ActionFailed (no detail)	Generic failure. The connector didn't return a useful message.	Open run details. Check PPAC Analytics. Test the same action manually. Inspect the raw error in Advanced view.
Delegation (Power Apps context)	Filter/Sort can't run server-side for this data source.	Use delegable functions. Add LoadData limits. Or move logic to a flow.

How to Read the Error in Run History

• Code: Often shown as statusCode or in the error message. "401" or "Unauthorized" both point to auth.
• Message: Read it. "The remote server returned an error: (401) Unauthorized" tells you the code and that it's auth-related.
• Correlation ID: Use this when opening a support ticket. Helps Microsoft trace the run.
• Inputs/Outputs: Compare what the failed action received vs what it expected. Null or wrong shape = 400/BadRequest.

Code Families: Quick Mental Model

Family	Codes	Your fix is usually...
Auth	401, Unauthorized, AccessDenied	Connection, permissions, or license
Config	400, 404, BadRequest, InvalidRequest, InvalidTemplate	Inputs, schema, or resource path
Throttling	429, Throttled, TooManyRequests	Slow down, add delays, retry
Temporary	500, 502, 503, 504	Retry, check service health

Microsoft Sources