Error convert to PDF - The remote name could not be resolved.

[Reason]

Problem in converting Word to PDF with One Drive Businnes.

Flow first fills the Word file with two variables, saves it, converts it to PDF, and finally sends it in a message.

I get the following error.

The remote name could not be resolved: 'mediagfx365-my.sharepoint.com'

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

{
  "Cache-Control": "no-cache",
  "Pragma": "no-cache",
  "Transfer-Encoding": "chunked",
  "x-ms-request-id": "f4c62603-2a70-4ae8-a754-87ac4404c07b",
  "X-AspNet-Version": "4.0.30319",
  "X-Powered-By": "ASP.NET",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "true",
  "x-ms-apihub-obo": "true",
  "Date": "Fri, 09 Sep 2022 15:01:13 GMT",
  "Content-Type": "application/json",
  "Expires": "-1"
}

Flow:

Results:

I do not see any rule as to why flow starts once and then does not.

Microsoft's technical support did not even make a notification within three days ...

What other connector should I use instead of OneDrive for Business?

Which will work. Word file has two text boxes to change and background as watermark. I don't know if it matters.

[grafferty]

Anyone seeing this issue again? I'm getting the same one happening 

[chicken_1]

seemed to take an absolute age for a single file, but it did convert sucessfully.

[grafferty]

Ok perhaps a local issue for us - thanks for checking

[Reason]

There are problems again.

[adamtj]

Still problem here...

[ZhanelIman]

@adamtj Hi, is problem recurring with all runs? Have you tried adding Delay action?

[ZhanelIman]

Hi, are you using Delay action?

[IvakaVT]

I have the same problems (error 400...) Yesterday few times but not every time like last week.

Yes I am using Delay function but after the HTML to PDF conversion step.

What is your point for this?  If I have the error the flow never proceed to Delay function.

[Mijanou]

I have seen no issues since the 14th. With over 50 daily runs there was only one instance where a retry occurred because of a bad request (2 min delay and retry built into the flow). Where before 5 retries were not enough. Microsoft support says that the product team started applying fixes globally.

[adamtj]

At first it was problem on all runs but now and it was more or less impossible to get it to work, failed on all reruns. But yesterday to run it again actually worked, it still got error on first run but it worked when i tried it again.
No i are not using any delay action.

[Kitsu]

This is still happening to me like 2 times in 25 runs, same error, I guess we need to use a payed connector until it is fixed 100%, i'm using delay of 5 sec....