Convert to PDF Failing

[Nicci]

Hi All, I have a flow that has been running for almost a year now. Today as of 2:40pm the flow stopped working and started failing at the Convert File step. Here is the error:

  "status": 404,

  "message": "Error from Office Service. Url=https://wordcs.osi.office365.us/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close\r\nDate: Mon, 22 Apr 2024 20:29:09 GMT\r\nServer: Microsoft-IIS/10.0\r\nX-Powered-By: ASP.NET\r\n",

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

I tried removing the step, adding it back, nothing. Is this a Microsoft issue or did something get updated/changed that I'm missing. Thanks.

[DrWhite]

I have same problem,, so at the moment , the unic solution is take it easy , and wait for the best and fast onedrive team!! 

[hoppPS]

I have also had the same problem since last Friday without any changes to the Flow. Before that, the flow had been running smoothly for over half a year. Adding the connector again or completely rebuilding the flow didn't help either - that's frustrating!

[paulbeck1]

I am waiting for a response from Microsoft on either my enterprise support ticket or my partner support ticket, on the OD4B Convert to pdf issue - hopefully I'll get and share an update today.

This is the exact same issue: 

Re: Converting file: Error from Office Service. - Page 2 - Power Platform Community (microsoft.com)

Here is a 3 min mp4 outlining the issue: https://youtu.be/bCaaTHSDxtM

[JamieD]

I've had this issue since mid-last week. Oddly, I found out today that my colleague, who works with different flows, hasn't.

I've spent most of today trying to isolate what the exact issue is. I've removed connectors and readded them, recreated entire flows, created brand new test flows and other things besides.

I've narrowed it down to this: It seems that older Word files (i.e. older than about a week ago) are able to be converted absolutely fine, no problems at all. But any Word files created or uploaded to OneDrive since then fail to convert, and produce the error reported. Interestingly, this includes old files (which work) which are downloaded and then reuploaded without any changes. Even Word files that I create directly in OneDrive fail to convert. However, if I copy an old file from one folder to another, converting it still works.

So for us, it seems to be an issue with the creation of word files somehow being different now, which is causing the Convert flow to fail.

Although my colleague's flows work perfectly fine. Maybe it's just certain OneDrives? Go figure...

[JamieD]

I've had this issue since mid-last week. Oddly, I found out today that my colleague, who works with different flows, hasn't.

I've spent most of today trying to isolate what the exact issue is. I've removed connectors and readded them, recreated entire flows, created brand new test flows and other things besides.

I've narrowed it down to this: It seems that older Word files (i.e. older than about a week ago) are able to be converted absolutely fine, no problems at all. But any Word files created or uploaded to OneDrive since then fail to convert, and produce the error reported. Interestingly, this includes old files (which work) which are downloaded and then reuploaded without any changes. Even Word files that I create directly in OneDrive fail to convert. However, if I copy an old file from one folder to another, converting it still works.

So for us, it seems to be an issue with the creation of word files somehow being different now, which is causing the Convert flow to fail.

Although my colleague's flows work perfectly fine. Maybe it's just certain OneDrives? Go figure...

[DrWhite]

THANKS,,but i have de same problem,, new document, and nothing!! 

[sophi1]

Spent ages trying to figure this out 😭 Then looked at another of my flows and saw it had same problem! Glad I found this thread now!

[hoppPS]

We have tested again in more detail with different users - for some the flow continues to work without errors, for others it generally no longer works. The solution for us was to delete the connection references to OneDrive for the affected users. This is now working for us for the time being!

Thx @Bobsta666 again for the final tip!

[sophi1]

The solution of deleting the connections hasnt worked for me. Could anyone tell me how i skip out the PDF convert and just use the Word doc? Which content would i use?

[paulbeck1]

@sophi1  The actions work differently, so when you replace the action, you may need to persist the docx file.  Basically, check you logic works as they (OD4B Convert and word Convert actions) do behave differently

[paulbeck1]

I have 2 tickets open with MS on this issue, since Thursday 25 Apr 2024), I got an update last night: MS are still looking into the issue.  I was hoping for more.  I do feel that MS are aware and are onto this now.

[jcarballo]

I have the same problem. Look forward to what MS has to say about this. Thanks everyone for sharing so much helpful feedback. 

[DrWhite]

At the moment ,, I have de same problem ,, 🙃🙃🙃🙃

[paulbeck1]

I've been out at a client all day, no calls or emails from MS support.  There is something odd going on at MS, normally support is quick and good.  And we aren't even getting replies.  So no response on my partner ticket or on behalf of my enterprise customers behalf, so no news not even an update 19:00 (GMT) 1 May 2024.

[jamesbrabbs]

I've got the same issue. No workarounds working. 

Very frustrating as i have multiple flows impacted

[Nicci]

If you are doing what I did and using premium for the word template anyways then use the word connector that converts it to PDF. That was my fix for this whole ordeal. Thats what I get for using a 'preview' connector I guess 😞

[paulbeck1]

No news from support as of 2 May 15:10, I have asked for feedback/an update again.  Hopefully it gets resolved/answered.

[DrWhite]

no .. no changes

[Baurmo]

I also had a call with the Microsoft Support today, but again no news regarding this issue 😕 

[sophi1]

I had a call with Microsoft yesterday for over an hour, he kept asking me to try different things, none of which worked. He didn't seem to listen that a lot of people were experiencing the same issue.