Convert file - The remote name could not be resolved

[flowslcaplikas]

Hello,

It ran perfectly yesterday. However today I wanted to run it again just to make sure everything is OK. But it spits error which I don't really know how to resolve. Any assistance would be good.

It's simple flow which takes Items from sharepoint and photos, converts to base64 and creates html table with images.

After that is done, I create file as html and parse it to convert file and then create file.

Everything works perfectly since yesterday, today it spits error when converting file.

[BClouded]

Hi,
I'm running into exactly the same problem. It's probably just some temporarily glitch at MS services somewhere.
Have some patience. 

Kr,
Bart

[afabregat_me]

Hi, I'm running exactly the same problem. Argh, I have spent a lot of time trying to figure it out, and nothing seems to work.

"status": 400,
"message": "The remote name could not be resolved: '****.sharepoint.com'",
"source": "api.connectorp.svc.ms"
}

[flowslcaplikas]

Yep after one day issues resolved itself. Probably problems with Microsoft API.

[afabregat_me]

Yes, it seems that everything works fine again 🙂 

@microsoft , could we know what was the origin of the problem? 
regards

Albert F.

[Dramalho]

The service seems to work sometimes and other times won't work. Has anyone else done something like Edit and save the flow or anything else? 

[lucalf]

Same problem ..

[afabregat_me]

Problem happens again 😞

{

  "status": 400,

  "message": "The remote name could not be resolved: 'XXXX.sharepoint.com'",

  "source": "api.connectorp.svc.ms"

}

Error details: 12 de set., 11:43 Duration 00:00:54 (GMT +2)

[wehrner]

We are having the same problem. It works 1/10 times since Friday 9th of September

[Kitsu]

MS fix this please 

[rrm1]

Same problem. I've been freaking out since friday, thanks for reporting.

Hope Microsoft fixes it soon.

[jpatel60]

Having the exact same problem. The flow is behaving erratically. Sometimes, it processes the word to PDF conversion and sometimes it spits out the same error as shown above. Hoping for a rapid fix from Microsoft...

[afabregat_me]

Now, it's working again:

the full response:

{

"statusCode": 200,
"headers": {
"Pragma": "no-cache",
"x-ms-request-id": "b7aae601-22b7-4aa4-b4f9-10439c8022b0",
"x-ms-file-name": "MjAyMjA5MTItMTAwNDA1LTI1LWp1c3RpZmljYW50LnBkZg==",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"x-ms-apihub-obo": "true",
"Cache-Control": "no-cache",
"Date": "Mon, 12 Sep 2022 22:04:24 GMT",
"ETag": "\"{CB8FE257-D866-4D71-9418-7E55136BDDC8},4\"",
"X-AspNet-Version": "4.0.30319",
"X-Powered-By": "ASP.NET",
"Content-Length": "141681",
"Content-Type": "application/pdf",
"Expires": "-1"
},
"body": {
"$content-type": "application/pdf",
"$content": "******"
}

[lucalf]

I confirm. I tried yesterday (Milan, Italy) and it worked.

I understand this is not a great value info but ....just to know... 🙂

[wehrner]

It's working from Stockholm as well this morning. Good job

[flowslcaplikas]

Does not working today 12 PM GMT+3

[TUL]

Not working in Belgium either. Any idea what the origin of the problem is?

[flowslcaplikas]

Problems with API from Microsoft side. Let's hope they fix it soon or release patch for this converter.

[wehrner]

Not working in Sweden from 11 am local time

[icom54]

Still not working in Belgium