Unanswered

How to see the real request when testing a flow connector

(0) Share

Report

Posted on by Community Power Pla...

I'm making a connector and i can only get a couple of the Get calls to work. the other ones keep returning error 404 but if i take the end of the call postman calls them fine. they are all imported from postman in the first place.

But i can't troubleshoot it becaue the host name has been replaced with:

https://msmanaged-na.azure-apim.net/apim/mii.20av.2diq.5f3ee98d4c5872260e.5fba384055278e1b82/2600644fbaf14

I have no idea where to go from here. I've spent foever and everything looks perfect. it's not authentication cause some work and some don't. I need to see what the real request to the server cause otherwise i have no idea how i can troubleshoot this

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

v-yuazh-msft on at

Like (1)

Report
Copy link

Link copied!

Hi @Anonymous,

I have made a test on my side and couldn't find a way to see the real request to the server, I afriad that there is no any way to achieve your needs in Microsoft Flow currently.

If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Best regrads,

Alice

Was this reply helpful? Yes No
GabrielStJohn on at

Like (0)

Report
Copy link

Link copied!

Hey, @Anonymous!

Thank you for posting on the Flow Community Forum! It appears as though @v-yuazh-msft would like some more information in order to further assist you properly with your issue. Please share any additional information that was requested in order to decrease the amount of time that it will take for you to be assisted!

Thank you for being an active member of the Flow Community!

-Gabriel
Flow Community Manager

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Copy link

Link copied!

While it would still be cool to see the whole request string when testing the custom connectors I solved my problems by making a new connection to the custom connector every time I changed ANYTHING. Don't know why that is but that is what worked. My api calls were all correct the connection was just failing.

Was this reply helpful? Yes No