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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,973)