cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JohnAageAnderse
Memorable Member
Memorable Member

Call Flow using PowerShelll asynchronous, how to poll?

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?

1 ACCEPTED SOLUTION

Accepted Solutions

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

View solution in original post

13 REPLIES 13
kojisaiki
Community Support
Community Support

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

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

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?

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

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)

コメント 2020-04-08 184250.png- When request in browser, response was shown after several seconds.

コメント 2020-04-08 184140.png

 

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

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

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

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 FlowDescription of the Flow

Setting of the HTTP responseSetting of the HTTP response

 

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

Thanks for your help.

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 🙂

Charles-Antoine.Flow with asynchronous response.jpg

Charles-Antoine.Flow with asynchronous response.settings.jpg

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

 

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:

FlowAsynch.png

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

FlowAsynchPostMan.png

Here is the GET call with the outputlink URI:

FlowAsynchPostManGET.png

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

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

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

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (3,494)