BadRequest. Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: 'australia.azure-apim.net''
Question
Thursday, July 6, 2017 11:52 PM | 2 votes
Since last night I have numerous MSFlow's failing all with the same error message.
BadRequest. Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: 'australia.azure-apim.net''
Specifically the actions I have found so far that are failing include:
- Post from Flow to Slack
- Flow mobile notification
- Flow email notification
Region is Australia. Please help
All replies (17)
Wednesday, July 12, 2017 12:10 AM ✅Answered | 1 vote
This issue appears to have resolved itself after about a week
Friday, July 7, 2017 12:49 AM
Same issue here, all previously created flows are showing the unplugged connection error logo but do seem to run correctly most of the time.
Any new flows fail with the above mentioned status code, have tested multiple tenants, multiple accounts.
Australia region also.
Friday, July 7, 2017 1:51 AM
Same for me too - flows can't find form names, error messages Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: 'australia.azure-apim.net''.
Richard P
Friday, July 7, 2017 2:40 AM
Glad it's not just me then. Hopefully they fix it soon. Not achieving a whole lot today with it broken.
Friday, July 7, 2017 2:53 AM
No sign of outage on Azure boards I can see.
Richard P
Friday, July 7, 2017 3:42 AM | 2 votes
I originally tweeted @AzureSupport who directed me to post here, and that they were escalating to eng. Fingers crossed.
Friday, July 7, 2017 6:35 AM
Still broken, but some new behaviour here, with a bit of additional information that I'm hoping may help MS fix.
Friday, July 7, 2017 12:29 PM
Could you send your API management service name and instances to this DL: Azure API Management apimgmt@microsoft.com, which will help to resolve the issue.
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
Saturday, July 8, 2017 5:14 AM
I have no such thing sorry. All of these problems are using native MF Flow actions and triggers.
Saturday, July 8, 2017 11:19 AM
To clarify: Which Azure service are you referring to (Azure web app or API Management)?
Could you elaborate bit more about the issue?
Saturday, July 8, 2017 10:54 PM
Using Microsoft Flow. Flows we're working fine then stopped. Error message is above.
Tuesday, July 11, 2017 1:27 AM
This issue is already resolved on my end. The server might have been down for a while.
Try to re-create the Flow by deleting the old one and adding a new one.
Make sure to select the Site Address and List Name from the dropdown box.
Tuesday, July 11, 2017 2:36 AM
If I recreate NOTIFICATIONS, they now appear to work.
If I recreate the failing actions to Slack or Mailchimp, they are still failing.
Tuesday, July 11, 2017 3:05 PM
I would suggest you to create a technical support ticket for better assistance. You can check this link for “How to create a support ticket”
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
Wednesday, July 12, 2017 8:17 AM
Glad to know that your issue has been resolved.
Wednesday, July 12, 2017 8:00 PM
But no word as to WHAT caused it appearing anywhere? Come on Microsoft, we have to be able to trust you're aware of these outages and working on them when they happen and the only way we know is if there's an outage bulletin somewhere.
Richard P
Wednesday, July 12, 2017 10:24 PM
This is what I received from support once the issue was escalated to a sufficient level
“We had an issue last week that resulted a batch if broken flows. It looks like this is one of those being affected. In the meantime, the current workaround is to recreate the flow.”