Power Automate – HTTP Error Codes (and what they mean!)

Power Automate - Solutions

Have you ever got an error code, such as 404, on Power Automate and had no idea what it means? This blog post is to show you what common error codes you can expect to see when using Power Automate with an easy to understand description of each!

If you’re unfamiliar with API’s, HTTP requests/methods and so on then this will help you understand the errors you may be facing on Power Automate, these are not specific action errors but the HTTP errors that can occur. There’s the error code and an easy to understand description provided below.

Error Codes:

400 Bad Request – 400 Status Code. You have provided incorrect data and the action endpoint has rejected it
401Unauthorized – 401 Status Code. You have provided incorrect or have not provided login details.
403Forbidden – 403 Status Code. You do not have access rights to the content but you have provided login details. You may simply not have the correct permissions.
404Not Found – 404 Status Code. You have tried to perform an action on something that does not exist.
405Method Not Allowed – 405 Status Code. This occurs when you try to use an action that the API is preventing (such as a HTTP method of DELETE).
406Not Acceptable – 406 Status Code. The action you have performed does not conform with the endpoints criteria.
407Proxy Auth Required – 407 Status Code. This is slightly more complicated as you will need a proxy to authenticate, you may need to reconsider your approach if this is required and you cannot change the endpoint’s settings.
408Request Timeout – 408 Status Code. This occurs when the endpoint you’re trying to contact may be having stability issues such as their server is offline.
409Conflict – 409 Status Code. Similar to 408, this is when your request conflicts with the state of the endpoint server (their server might have gone down!).
414URI Too Long – 409 Status Code. The Uniform Resource Identifier (URI) or URL is over the limit the server will except.
429Too Many Requests – 429 Status Code. This can occur if you’re running a Flow a lot of times and you get ‘rate limited’ by the endpoint.
500Internal Server Error – 500 Status Code. An error has occurred that the server does not understand how to handle.
501Not Implemented – 501 Status Code. The HTTP method you’re trying to use with an action or trigger is not supported.
502Bad Gateway – 502 Status Code. If you’re using a gateway, this can occur when a request gets an invalid response.
503Service Unavailable – 503 Status Code. You might experience this if the API endpoint is under heavy-load or down for maintenance.