Solved: PowerAutomate HTTP action requiring status code 200

PowerAutomate HTTP action requiring status code 200

I built some custom APIs using Azure Functions and want to access them in a PowerApp using a PowerAutomate Flow.

One of those APIs receives an image, stores it to the Blob storage and passes it over to a Cognitive Service API. As a result, I am getting an HTTP 202 (Accepted) response, which my own API will return to the flow.

The problem is now, that obviously the HTTP action in the Flow requires a 200 OK status code to move on to the next steps. So when it receives a 202, it automatically waits until the resource at the given location (Location header in the 202 response) returns 200.

This is not intended to be done, because checking this resource should be done in another step further down the flow and I still need the Location header for the further steps.

So, I have a few options:

Misuse the HTTP 200 status code to return "OK" even if the process hasn't finished yet (just so that the Flow moves on)
Rebuilding my whole architecture to fit PowerAutomate

Or: the HTTP action in the Flow does what I expect from an HTTP action: performing an HTTP request and returning the result (no matter what status code might be returned) and not interpreting the status code and acting upon it on its own initiative.

My questions:

Is it right that the HTTP action is waiting for a 200 status or am I getting anything wrong here?
If so, why does the HTTP action act upon the 202 status on its own?

Quick Links

Leaderboard