Showing results for 
Search instead for 
Did you mean: 
New Member

Flow trigger failing in flow, but Test succeeds

I have a custom connector to a Web API on my local machine. It is accessible from internet. On testing the trigger with a sample callback url, it succeeds.

However, when I use the trigger in a flow, I get an error "404 not found". Here is the error in detail - 

  "error""{\r\n  \"code\": 404,\r\n  \"message\": \"Unable to match incoming request to an operation.\",\r\n  \"source\": \"\",\r\n  \"path\": \"\",\r\n  \"clientRequestId\": \"346737e5-1f09-4381-86ce-9d13bba912c4\"\r\n}"


Any one faced similar issues?

Community Support
Community Support

Hi @iashishi,


Could you please share a screenshot of your flow's configuration?


The error message told that the Open API could not match the incoming request to an Operation that you specified within your custom connector (Operation Not Found), it is a configuration issue. More details about this issue, please check the following article as a reference:


Please check if you have created a proper trigger within your custom connector. More details about how to define triggers or actions (operations) within your custom connector, please check the following article:


In addition, if you use API key authentication within your custom connector, it is not recommended to test the connector immediately after you create it, it can take a few minutes until the connector is ready to connect to the API. please check the following article as a referene:



Best regards,



Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Kris,

I am not sure how to attach screenshots here.

If the definition of the trigger is not proper, shouldn't the "Test" step fail? As I said earlier, the "Test" step in connector configuration is working fine.

Anyway, I have raised a support ticket with Microsoft. The support team has not been able to figure the issue in two days now. So, I am pretty sure it is not a simple configuration issue but a deeper problem( bug) in Microsoft flow.

I will update this thread once I receive solution from Microsoft support team


Ashish Iddya


Helpful resources

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 (13,462)