Given:
- we have private REST service
- we installed and configured On-premises gateway
- we created Custom REST Connector
- everything works fine without usage of Asynchronous Pattern
When:
- we tried to enable Asynchronous Pattern
- and our long running operation returned 202 and location header
Then:
- Power Automate failed
- with an exception "The host name '10.1.xx.xx' resolved to IP address '10.1.xx.xx' which is restricted."
We also are not able to configure polling `trigger` with On-premises gateway
Thanks for reporting this issue!
Looks like an issue on how the Location header is translated and a gap in our platform.
To whom it may concern,
to avoid this issue you also need to configure another endpoint in Custom REST Connector
that matches the URL for status endpoint returned in location header
and enable On-premises gateway in this endpoint.
In this case Custom REST Connector will use On-premises gateway
and will correctly route private IPs like 10.1.xx.xx