You’re offline. This is a read only version of the page.
9
Hi,
I've noticed my custom connectors return a 500 error with the following message :
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond {ip address}
This message also happens when I call the custom connector's action in "Test" section.
I tried to execute the same request with the step "HTTP". (Same authentification parameters, same url and query parameters...) It executed correcly. So I deduced the problem wasn't my external service denying access to Power Automate.
Then I tried to change the Connection created. It didn't solve the problem.
Finally, I tried to just request a single GET url that didn't require any kind of authentication. I created a new Custom connector and after defining it, I executed it with the "Test" section. I still managed to get the error.
Everything worked fine for 2 years until today.
It seems to happen to any custom connector I'm creating. Was there any update from Microsoft that might be the cause ? Or am I missing something to solve the issue ?
Turns out power automate uses servers with different IPs and it decided to suddenly changed the IP, explaining the problem
Share
Report
All responses (
Answers (
