cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
webdes03
Frequent Visitor

Unable to match incoming request to an operation.

I have an OpenAPI definition (Swagger) for an anonymous endpoint (authenticated by providing a licenseId and appId as header values). This OpenAPI definition works with Logic Apps and Nintex Workflow Cloud, but not with Flow. I imported the defintiion, and set security to none (same exact steps as Logic Apps), all of the operations are correctly identified, but when I test it I get odd/incorrect results.

 

The request url should be https://dev-api.elasticocr.com/v1.0/jobs/{jobid}, but Flow is sending it to msmanaged-na.azure-apim.net

 

Request

Url:

https://msmanaged-na.azure-apim.net/apim/elasticocr.20.2d.20dev.5fae991b2e953c45e5.5f0447122807b1e5c...[jobid]

 

Headers:

 

{
  "Authorization": "Bearer {token}",
  "licenseId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "appId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy"
}

 

licenseId/appId removed for security purposes, but I can't figure out why it's sending the request to a different domain, and why it's including a bearer token given that the API is technically anonymous. We do not see these issues in Logic Apps, only in Flow.

 

Security is correctly configured:

2018-04-13 10_57_15-Manage your custom connectors _ Microsoft Flow.png

As a result of the wrong request URL, the response is obviously also incorrect:

{
  "error": "{\r\n  \"code\": 404,\r\n  \"message\": \"Unable to match incoming request to an operation.\",\r\n  \"source\": \"msmanaged-na.azure-apim.net\",\r\n  \"path\": \"\",\r\n  \"clientRequestId\": \"53c6068c-9566-4b87-8311-c117-0304008c\"\r\n}"
}

 

I have seen a few reports that msmanaged-na.azure-apim.net/apim is used as a proxy if the API is protected by OAuth, but in our case it obviously isn't and security is set to none, so I'm baffled as to what's going on here. Any advice or insight is appreciated.

 

7 REPLIES 7
webdes03
Frequent Visitor

Follow up: I created a postman collection with just a single one of our endpoints in it, and tried importing that into Flow and get the same behavior. So it's definetely something on the Flow side.

v-yuazh-msft
Community Support
Community Support

Hi @ webdes03,

 

Could you please share a screenshot of the configuration of your flow?

 

Do you mean the flow would send the request to a different domain? tThe request url should be https://dev-api.elasticocr.com/v1.0/jobs/{jobid}, and the Flow is sending it to msmanaged-na.azure-apim.net:https://msmanaged-na.azure-apim.net/apim/elasticocr.20.2d.20dev.5fae991b2e953c45e5.5f0447122807b1e5c...[jobid]?

 

Could you please share more details and screenshots with us?

We would try to offer you a proper workaround if you could share more details and screenshots with us.

 

 

Regards,
Alice Zhang

@v-yuazh-msft unfortunately I can't even get past testing the connector, so I haven't even gotten to trying to put it into a flow.

 

At one point the requests randomly started returning 200s and 201s (which is the way it should work). But I have no idea what I did to make it work. I thought maybe Flow had cached an old/bad version of our Swagger definition. Then I deleted the connector and rebuilt it and it's back to not working again.

 

The simplest endpoint in our Swagger definition is one that validates a license. It takes a header paramater for a License ID and App ID, and returns a license response if the license is valid. This is the endpoint I've been using to test the connector since it basically has no moving parts.

 

As you can see, if I test the endpoint through Swagger's integrated testing functionality, the endpoint works as expected. It should also be noted that this API works in all of our native apps, as well as with Logic Apps and Nintex Workflow Cloud. Flow is the only platform we're having issues with.

 

MSFlow-Swagger-License.fw.png

 

As you can see from the Swagger test, the request URL should be:

https://dev-api.elasticocr.com/v1.0/license

 

If I now go to Flow and test that endpoint, we see that the Request URL is incorrect, and Flow returns a 404 claiming the request can't be matched to an operation.

 

MSFlow-CustomConnector-Request.fw.png

 

MSFlow-CustomConnector-Response.fw.png

 

If I had to theorize what's going on... Flow is modifying or changing the request that gets send to our API. We don't do any sort of source checking, so even if Flow is sending it through a proxy (which I suspect is what the msmanaged-na.azure-apim.net URL is), it shouldn't matter on our end. Even then though, as I understood it Azure Logic Apps and Flow are incredibly similar under the covers, so I certainly can't explain why everything validates in Logic Apps, but not flow.

 

2018-04-16 10_37_43-Logic Apps Designer - Microsoft Azure.png

 

I'm really tearing my hair out here... there's no rhyme or reason as to why it shouldn't work. The API is technically anonymous, save for the License ID and App ID headers, so there's no authentication (OAuth, etc.) in play. I've also tried scrapping our Swagger Definition and just creating a Postman collection with only the Get License endpoint in it, and I get the exact same behavior.

Hi @webdes03 - could you send me a link to the swagger or attach it in a direct message? The ID of your custom connector in Flow would also be usefuly (found in the URL when you're editing the connector). Unfortunately there's a known issue with users hitting a 404 immediately after creating or updating the operation however that should be temporary (<5mins). If you're continuing to see the issue something else may be wrong. We do route all the requests through our central system before your API, so the "msmanaged-na" URL you're seeing is expected, however the correct parameters etc. should ultimately be forwarded to the API as you described. Once you send it over we'll try to reproduce it on our side and get to the root of the issue.

@tpalmer - Absolutely... I'll DM you a link to the Swagger and a valid license you can test with. Ironically, it does seem to be working now, so perhaps we were just being bitten by your temporary 404 issue. Nevertheless, if you're willing I'd love to have you try it from your end to confirm.

Yes them 404 errors are priceless. You are never quite sure if you should continue to troubleshoot, of if you should go and have coffee and hope for the best  Smiley Happy

Anonymous
Not applicable

I'm getting the same issue with a new Custom Connector for PowerApps. I formed the json and created the new connector without too many dramas though the open api document I created was not supported so I had to implement a number of changes in the json file, but that all works and is added to PA, however, I get a 

 

{
"error": {
"code": 404,
"message": "Unable to match incoming request to an operation.",
"source": "msmanaged-na.azure-apim.net",
"path": "",
"clientRequestId": "fe82a0f2-49a9-4d10-908d-3974ae08aeaf"
}
}

Session ID: 2e1f8645-0d00-4865-8cf5-92d3ca370f42

 

Now for any new data sources that I try to add (it will  only want a sharepoint data source or spawn this error), and it has been going on for about an hour (I've used a number of browsers including incognito). The only way I can get the data sources back is to kill the most recent PA session, and restart it but the error keeps coming back.

 

I am trying to get PA to send back drawing pen doodles to Sharepoint.

Cheers,

Richard

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!

Top Kudoed Authors
Users online (3,157)