cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Regular Visitor

Asynchronous Pattern - "404 - Resource Not Found"

Hi All,

 

 Trying to get a custom connector to  support "Asynchronous Action" pattern using "202 Accepted" and a location header. Reading up on this in various blogs and Microsoft articles, all I needed to do was to return 202 and have a location header / retry-after sent back. While Flow does to retry, it always throws a 404 Resource Not Found error. Question is, do I need to define the URL in the location header in the OpenAPI definition as well? Strangely if I send a relative URL back, then Flow is fine, but doesn't wait to retry and just carrys on. What am I doing wrong? 

2 REPLIES 2
Highlighted
Community Support
Community Support

Hi @EswarPrakash,

 

Could you share more details on the error message?

How is your custom API configured?

I assume that you need to define the URL in the Open API definition so that the connector can use the base URL to determine how to call the API.

Hope the following doc could be your reference:

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Advocate I
Advocate I

Make sure the location URL is pointing to an api in your swagger definition (the api can be marked as 'internal' if don't want to expose it to users)

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Users online (9,691)