cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Stop Flow sending a 202 response

Hey,

 

We have a Flow that's triggered upon receiving a http request.

 

We have some trouble caused when Flow responds with a 202 after receiving the request. The sending service can't process the response body as it's expecting xml/soap, not JSON. This then later causes the service to attempt retries, which don't succeed for the same reason (receiving an unreadable JSON body).

 

We were wondering if it was possible to disable the automatic 202 response, or if not, if there's somewhere we can customise the body of the response so that it can be processed correctly.

 

Cheers,

Connor

21 REPLIES 21
ChristianAbata
Most Valuable Professional
Most Valuable Professional

hi @Anonymous  please see that the responses are configured on the server. So if you can modify your server you can change your response.



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me:
Youtube: Christian Abata
Facebook: Power Automate LA
Website Tutorials: Christian Abata
Anonymous
Not applicable

Hey Christian, 

 

Thank you for your response!

 

Is there any documentation/links you could provide for the server settings? 

 

Cheers,

Connor

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

The service is expecting xml/soap format and looks like you are passing JSON format. Check the documentation of the http service you are calling. Also try the request in POSTMAN tool and test the http request. Looks like you are using the wrong format for the submission.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Forgot to add this link earlier.

 

https://restfulapi.net/http-status-202-accepted/

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm,

 

Thank you for your response!

 

We're aware that the service is returning JSON when expecting xml/soap, but as far as we can currently see, there's no way to control this response as it's not being sent by us, but rather automatically when the Flow is hit?

 

We have our own `Response` action which is returning a 200 and the appropriate xml/soap response body, but it seems like the automatic 202 response is superseding our own response.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Could please explain the scenario? 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm,

 

We have a flow with the `When a HTTP Request is received` trigger.

 

It appears that when this flow is hit, a 202 response is sent with a JSON body - I'm not sure if we have any control over this, as it's not coming from any `Response` action within the Flow.

 

Due to this seemingly automatic 202 response, the service that sends the requests is processing the response as an error because it's not in the correct format, i.e. xml/soap.

 

We wanted to know if this automatic response is configurable anywhere - ideally we would turn it off and respond ourselves with the `Response` action.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your reply.

 

You could try the following:

 

1. Can you capture the response? If you can then check the response and do the relevant actions.

2. What happens when you get 202 is that current flow step fails? Then set the exception features of flow.

 

If you don't know how to set the exception handling then let me know. A screen share will be ideal. It's easier to explain via screen share.



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
ChristianAbata
Most Valuable Professional
Most Valuable Professional

hi @Anonymous maeby if you can share with us an screanshot could me more cleare what you need. ;D



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me:
Youtube: Christian Abata
Facebook: Power Automate LA
Website Tutorials: Christian Abata
Anonymous
Not applicable

Hey,

 

When we make a request using Postman we instantly receive a 202 response from Flow with the JSON body:

 

{
    "properties": {
        "waitEndTime": "2020-02-25T15:17:21.083361Z",
        "startTime": "2020-02-25T15:17:21.083361Z",
        "status": "Running",
        "correlation": {
            "clientTrackingId": "08586189630443963198638270456CU65"
        },
        "workflow": {
            "id": "-",
            "name": "08586189782022726395",
            "type": "Microsoft.Logic/workflows/versions"
        },
        "trigger": {
            "name": "manual",
            "inputsLink": {
                "uri": "-",
                "contentVersion": "7JqVSbZmODxJq2vRpAlXzA==",
                "contentSize": 29,
                "contentHash": {
                    "algorithm": "md5",
                    "value": "7JqVSbZmODxJq2vRpAlXzA=="
                }
            },
            "outputsLink": {
                "uri": "-",
                "contentVersion": "BaKHXBjJs87+9WPsHl17hg==",
                "contentSize": 275,
                "contentHash": {
                    "algorithm": "md5",
                    "value": "BaKHXBjJs87+9WPsHl17hg=="
                }
            },
            "startTime": "2020-02-25T15:17:21.0666984Z",
            "endTime": "2020-02-25T15:17:21.0666984Z",
            "originHistoryName": "08586189630443963198638270456CU65",
            "correlation": {
                "clientTrackingId": "08586189630443963198638270456CU65"
            },
            "status": "Succeeded"
        },
        "response": {
            "startTime": "2020-02-25T15:17:21.0822622Z",
            "correlation": {},
            "status": "Waiting"
        }
    },
    "id": "-",
    "name": "08586189630443963198638270456CU65",
    "type": "Microsoft.Logic/workflows/runs"
}

 

Is there a reason this comes through? 

 

We're using the trigger: https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-actions-triggers#request-trigg...

 

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Can you see this response in Flow? Also a screen shot will be helpful here.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm,

 

Not sure what you mean or where to see it - there's no `Response` action in Flow, only our `When a HTTP request is received trigger: 

 

flowwwww.png

 

Cheers,

Connor

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thank you for the screenshot. 

 

I can see from the run history you have something inside the body (SOAP XML).

 

What's your next step of action when you receive this? In order to understand better can we do a screen share? If not that's fine.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm 

 

Sorry - as it's handling sensitive data I think it would be best to not screenshare, but if it helps I can let you know that:

 

- We receive Soap XML, and then read this into a few different variables (using xpath/xml functions)

- We then do some basic processing on this data and send it to our Data source

 

We had previously had a `Response` action immediately after receiving the request, but the 202 was still sent before the Response action we had. In our Response option we were setting a 200, content-type xml, and giving the correct body back.

 

Our real question is where the 202 response is coming from, and if it's something that's configurable outside a single individual Flow in some kind of admin centre?

 

 

 

This confuses us, as we're simply not sure where the 202 is coming from.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your reply.

 

This might explain why you getting this.

 

Your logic app keeps the incoming request open only for one minute. Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a 504 GATEWAY TIMEOUT to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a 202 ACCEPTED response to the caller.

 

https://docs.microsoft.com/en-us/azure/connectors/connectors-native-reqres

 

 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm ,

 

Ah okay - so in the past when we had the `Response` action, we still saw the 200's coming through but I wonder if the high levels of requests we are handling could cause a delay in sending our own Response, causing the 202 to be sent?

 

I would assume that then our 200 would later be sent when the Flow reaches it at a later point.

 

Would the below be possible:

  • We send a 202 because it takes more than a minute to process the request (due to the high load)
  • This causes the service sending the request to interpret it as an error, and schedule a retry for later on
  • We eventually send the 200 Response that we defined, but at that point the request is already rescheduled for a retry

 

I can re-add in the `Response` action to see if it fixes the issue, but if it works as before I'm not sure if we'll see a change in behaviour.

 

Thank you for all of your responses!

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

202 means the request has been accepted for processing, but the processing has not been completed. 

 

Yes add that response back in and see whether its working or not.

 

Please see this. Some good discussions around this especially POST return 202 with return a URI where client can utilise this and use GET to return the results.

 

https://stackoverflow.com/questions/4099869/is-it-wrong-to-return-202-accepted-in-response-to-http-get

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hey @abm 

 

So I've just setup a basic Flow which receives a HTTP request, and then Responds:

 

flow.png

 

After a quick test with Postman, I still receive a 202 instantly in response.

 

I guess this behaviour isn't configurable, and Flow will always send a 202 back?

 

Our problem is we aren't in control of how the service that is sending requests to Flow handles the responses - it has no problem with the 202 code, but with the JSON body that comes with it.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for the update. The target system need to identify whether its 202 or 200? Looks like 202 is not by default. I have used similar flows in the past but not as POST. 

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders   UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

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.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (2,703)