web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Custom Connector with ...
Power Automate
Unanswered

Custom Connector with On-Premises Data Gateway + Route Request Policy Fails

(0) ShareShare
ReportReport
Posted on by 112

Hi folks,

 

This is a doozy. Please bear with me as the issue is dense. 

 

I have created a custom connector that connects to a public API. I have made use of the Route Request policy to enable multiple actions that go to the same endpoint, which is a common workaround. The endpoint's format is /deployments/api/resources/{resource_id}/requests.

 

This has been working successfully for over a year, with no problems. Our company is moving to an on-premises version of this API. The API reference is exactly the same. In order to enable this, all I have done is change the "Host URL" and modify the connector to require use of an on-premises data gateway. So far so good. 

 

I am able to send requests to the on-premises API without issue. However, when I attempt to use the Route Request policy, this fails with a 404 and throws the error "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

 

At first I thought something about my request was being malformed by Route Request, resulting in the error. I tried:

1. Sending a request without Route Request applied to the .../deployments/api/resources/{request_id}/requests endpoint. This is successful. 

2. Checking in both Power Automate and the Custom Connector "Test" tab. Both return the same result. 

3. Enabling Additional Logging on my on-premises data gateway and reviewing the QueryExecutionReport logs. Mysteriously, the requests that throw a 404 and give the "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable." error are not ever sent to the gateway. 

 

My thought is that the "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable." error is being returned by Power Automate/Azure Service Bus due to some sort of incompatibility (perhaps with on-premise data gateway?).

 

My questions:

1. Is the Route Request feature supported for the on-premises data gateway?

2. If so, what could be causing this behavior? Why would Power Automate return this error when I am sending a valid request?

 

Any help would be greatly appreciated, thanks!

 

Categories:
I have the same question (0)
  • sshinya Profile Picture
    4 on at

    Hi @ell10706 ,

    I’m facing the same issue with my custom connector using the Route Request policy and on-premises data gateway. When I send requests through the gateway, I get a 404 error.

    Have you found any solution to this problem? 

  • sshinya Profile Picture
    4 on at

    I wanted to add some additional information that might help us troubleshoot this issue further:

    Evidence:
    * We have implemented logging on the API side, so we can analyze the access logs. However, when using the Route Request policy, there are no access logs, which suggests that the request might not be reaching the API from the on-premises data gateway.
    * Additionally, there are no logs on the on-premises data gateway, indicating that the request might not be reaching the gateway itself.
    * When the on-premises data gateway is enabled, the query is first sent to the gateway and then forwarded to the target resource. See On-premises data gateway architecture | Microsoft Learn

    Hypothesis:
    It seems that when using the Route Request policy, the destination set in the gateway is being overwritten by the Route Request destination, causing the request to fail.


    Any insights or solutions you might have would be greatly appreciated.

  • blanghorst Profile Picture
    206 on at
    I'm seeing the same issue.  Did you ever find a solution?  The "Set host" template states in the documentation that it won't work through a gateway but I don't see the same note for Route Request.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 519 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 296 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard