Call Flow using PowerShelll asynchronous, how to poll?

[JohnAageAnderse]

Created a flow with the "When a HTTP request is received" trigger. 

The flow has been setup to response asynchronous. The flow is called using PowerShell method Invoke-RestMethod. The response received contains this information (partly):

id=/workflows/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz/runs/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

properties.status=Running

It is understood that to poll for the final status, the method Invoke-RestMethod is used again with the above URL from id - plus the api version parameter (known).

Unfortunately the response gives the error:

Invoke-RestMethod : {"error":{"code":"DirectApiAuthorizationRequired","message":"The request must be authenticated only by Shared Access scheme."}}

Anyone knows how to correctly poll the flow for status update?

[kojisaiki]

According to docs, I suggest you to ask in github issue page.

And I suppose to it is good idea to look for similar issue before post your issue 🙂

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/sample-crisis-communication-app#issues-...

> Issues and feedback

• For feedback about the Crisis Communication sample template, go to aka.ms/crisis-communication-feedback.
• To report an issue with the Crisis Communication app, go to aka.ms/crisis-communication-issues.

[JohnAageAnderse]

Hello @kojisaiki 

Thank you for your reply, but ... my flow and calling it from a PowerShell script has nothing to do with that application!

In the Response action settings it is stated:

Asynchronous Response
Asynchronous response allows a Logic App to respond with a 202 (Accepted) to indicate the request has been accepted for processing. A location header will be provided to retrieve the final state.

It is the part "A location header will be provided to retrieve the final state" that baffles me - how to use it correctly?

Kind regards, John

[kojisaiki]

Sorry, I just made a mistake in reply to another post... 😢

Let me know your question.

If you get a 202 response by kicking your Flow, is any destination URL or id for check progress included in the body or header of the same response?

[JohnAageAnderse]

Hello @kojisaiki 

Thank you for asking - it made me look at the response information closer and there I discovered the URL to use for the polling!

In the initial response, a StatusCode of 202 is received, which is good. But another field is provided - Content - which contains JSON. Examination of this lead me first to not see the URL to use - so my fault 🙂 Anyway, the path to the URL to use is:

Content > properties > trigger > outputsLink > uri

This gives me "https://prod-07.westeurope.logic.azure.com:443/workflows/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz/runs/xxxx..." which I can use to GET the status of my flow.

Kind regards, John

[kojisaiki]

One more, in my env, when add "Response" action on finish the flow, response of hook (trigger) URL has returned after finish the flow. If you can add  "Response" action on finish of your flow, probably you will not have to poll.

- My http triggered flow (it takes several seconds since in "Do until" section)

- When request in browser, response was shown after several seconds.

[JohnAageAnderse]

Thank you @kojisaiki  for the additional information.

I had that already, but the PowerShell script did time out due to my flow taking too long to response. So to avoid that, it was decided to go for the asynchronous method.

Kind regards, John

[Charles-Antoine]

Hi @JohnAageAnderse ,

I'm looking to do the same (my flow last longer than 120 secondes), can you give me a few details ?

 - Do you need to do something specific to get an asynchronous flow or no "Response action" means it's not synchronous ?

 - When I trigger the flow using the curl command, the response does not return any URL but a list of variables/ID:

HTTP/1.1 100 Continue

HTTP/1.1 202 Accepted
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
x-ms-workflow-run-id: 08585XXXXXXXXXXXXXXXXXXXXXX
x-ms-correlation-id: 9a2f937aXXXXXXXXXXXXXXXXXXXXXX
x-ms-client-tracking-id: 08585XXXXXXXXXXXXXXXXXXXXXX
x-ms-trigger-history-name: 08585XXXXXXXXXXXXXXXXXXXXXX
x-ms-execution-location: westeurope
x-ms-workflow-system-id: /locations/westeurope/scaleunits/prod-11/workflows/edf01eXXXXXXXXXXXXXXXXXXXXXX
x-ms-workflow-id: edf01eXXXXXXXXXXXXXXXXXXXXXX
x-ms-workflow-version: 08585YYYYYYYYYYYYYYY
x-ms-workflow-name: a277c0ee-XXXXXXXXXXXXXXXXXXXXXX
x-ms-tracking-id: 9a2f937a-XXXXXXXXXXXXXXXXXXXXXX
x-ms-ratelimit-burst-remaining-workflow-writes: 279
x-ms-ratelimit-remaining-workflow-download-contentsize: 201326592
x-ms-ratelimit-remaining-workflow-upload-contentsize: 201280941
x-ms-ratelimit-time-remaining-directapirequests: 18749596
x-ms-request-id: westeurope:9a2f937aXXXXXXXXXXXXXXXXXXXXXX
Strict-Transport-Security: max-age=31536000; includeSubDomains
Date: Thu, 08 Oct 2020 15:38:58 GMT
Content-Length: 0

Is there a way to create the URL with these IDs ?

Thanks for any info you can give !

Best regards

[JohnAageAnderse]

Hello @Charles-Antoine 

In your flow, all response actions must be set to asynchronous (it will complain otherwise).

Your Curl call should then receive the content also.

If you have already tried this, kindly enlighten us 🙂

Kind regards, John

[Charles-Antoine]

Hi @JohnAageAnderse ,

Thanks for your reply. I found the setting "Asynchronous" in the response Action and when I trigger the flow with the curl, I receive a 202 return and the properties/trigger/outputsLink/uri link in the JSON.

When I do a GET with this uri, I have (the body is the exact content sent from the post) :

{"headers":{"Connection":"keep-alive","Accept":"text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2","Host":"prod-187.westeurope.logic.azure.com","User-Agent":"Jersey/2.4.1,(HttpUrlConnection 1.8.0_261)","Content-Length":"279","Content-Type":"application/json"},"body":[{JSON sent from the POST}]}

Here are some screenshots of the flow and of the response setting:

Description of the Flow

Setting of the HTTP response

I feel like I'm really close but I must be missing something...

Thanks for your help.

[JohnAageAnderse]

Hello @Charles-Antoine 

Place your response as the last action in your flow (see my flow below). Also don't change the Status Code, keep it as 200. When the setting Asynchronous Response is turned on, it will return the Status Code 202 automatically. When the flow finishes, the Status Code 200 will then be used 🙂

When your script receives the 202 response, you have to look in the Content (JSON) and locate the URI to use - is should be this path in the JSON:

Content > properties > trigger > outputsLink > uri

Kind regards, John

[Charles-Antoine]

Hi @JohnAageAnderse ,

I updated the flow with your advice (response at the end, default status code) and I'm getting outputsLink/uri.

But the GET on this uri is still not giving me the status 😢.

I created a new basic flow:

Here is the POST call from Postman where you can see the status 202 and the properties/trigger/outputlink/uri

Here is the GET call with the outputlink URI:

And I get the same result if the flow is running or finished.

Could you show me the result of the GET in your case ?

It's driving me crazy, I don't understand what I'm missing. Thank you for your patience !

Best regards,

Charles-Antoine

[JohnAageAnderse · Accepted solution]

Hello @Charles-Antoine 

I rechecked my information and it turns out that I have given a incorrect solution to my own query 😕

The URI to use is in the Headers! In the Headers, in the Location property, you will find the URL to use. Funny is that this information was passed on to my colleagues, but somehow I got it incorrect into the solution post in this thread! My fault!

Anyway I also finally managed to find the Microsoft documentation for this:

https://docs.microsoft.com/en-us/azure/architecture/patterns/async-request-reply

This should help you solve your issue and I will mark this post as a solution for future viewers.

Kind regards, John

[Charles-Antoine]

Thanks @JohnAageAnderse , I got the URL in the header and it's working perfectly fine !!

Thank you again for your patience.

Best regards,

Charles-Antoine