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.

[AlexEncodian]

@Nicci 

Based on the number of people experiencing this issue despite flows running fine historically, I can only assume this is a Microsoft bug. 

Some fixes have worked for some users but others reported these did not help. 

1) Delete OneDrive connector actions, readd and remap fields

2) Recreate the Word template (if you're populate Word files)
Error from Office Service. Url=https://wordcs.offi... - Power Platform Community (microsoft.com)

I would also raise a ticket with Microsoft. Besides re-creating the entire flow from scratch, you could temporarily use a third party connector if you have low volumes (Encodian has 50 convert operations free per month)

Convert Word – Encodian Customer Help

[Talus]

I started having this exact same issue starting yesterday:

---

Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close

---

[Nicci · Accepted solution]

Yup it seems the consensus is it's a Microsoft issue. What I ended up doing was using the Word doc to PDF connector instead. Its premium but I was already using premium to fill a word template. That worked for me, so all good now! The convert to PDF is in preview so maybe its just bugged at the moment.

Updating - As of 5/9/24 this seems to be fixed now. If you delete everything in your temp and re-add the connector should be back in business.

[Talus]

I recreated the entire flow and the same error occurred.

I am using a Word template in my flow and I'm populating the fields using the SharePoint library metadata workaround as I do not have access to premium connectors.

As for recreating the Word template, would I be able to simply make a copy of the template with a new file name and use that in my Flow or should I start from scratch?

Thanks!

[Nicci]

I believe you can just make a copy of the template and use that, but ya without premium i'm not sure if there's a work around to convert to PDF once you're done as the only other one I saw that works is the word to PDF premium.

[Talus]

Ok. I made a copy of the my template and used that in my Flow. Same error occurred.

So it looks like I'm waiting on Microsoft to fix on their end at this point...

Thanks for the help!!

[Pecorre]

Same thing here. The problem started yesterday. I basically tried to rebuild everything from scratch this morning and nothing works. It's a big problem for me because this flow will be used by at least 100 users in the coming days...

[AlexEncodian]

@Talus / @Nicci 

Just to clarify, there are "Premium" connectors which require premium Power Automate licensing (the opposite being "Standard" connectors). Microsoft's own Populate Word is Premium.

There are also 3rd party connector that may require 3rd party licensing. 

3rd party connectors can be Standard or Premium. Encodian is a Standard connector so does not require premium licensing to use (but it is 3rd party so will require a license above a certain usage volume that is free).

Encodian has a Populate Word Document action that's not premium as well as convert actions.

[Bobsta666]

I think i may have found the solution!!!

Delete the connection from OneDrive in the home page left section under "Connections" and then in the flow re-establish a connection with OneDrive.

I was stressing about this for ages as it was the only step that failed causing the whole flow not to work.

Hopefully this works for you too

[DoubleT]

Thanks @Bobsta666  for sharing this solution! I was able to delete all the OneDrive connections in the environment and established a new connection inside the flow, this solved the issue for me.

[ChrissyL]

Hi Bobsta666, Can you advise how you re-establish a connection with OneDrive, is this just a premium facility or can I do it in standard?

[Bobsta666]

It’s a standard feature, on your power automate Home Screen (or any screen for that matter) on the left in the section below “flows”, expand it and you should see connections, click that and it will take you to the page where all connections are. Delete the one drive for business or whatever version you are using, it will ask are you sure as some flows may be using this connection, say yes. When you return to your “broken” flow it will start auto reconnecting. This fixed my issue, hopefully the same for you

[Bobsta666]

Or just add a flow with OneDrive as a component and it will ask to sign in

[patttachai]

Hi All,

Not everyone who delete -> re-add connection will get this bug resolved. I and many still get same error 404 not found. Please help escalate this to MS so they will fix this ASAP.

[karl91]

Hello everyone,

i can also confirm that deleting and readding the OneDrive for Business connection did not solve the problem. Still getting the same error output like @patttachai. 

[paulbeck1]

I raise a support ticket with MS yesterday, and last night they got back to me with "We checked internally and it is the outage from the OneDrive team"  The case has been transferred to the OneDrive team, and i'm hopeful the service shall be restored and the flows start working again. 

[paulbeck1]

post the msg again by mistake

[einfante]

Could you please update us when you get a response?

Thanks!!

[Volt26]

I tried to delete the connections and it didn't work

Then I tried again and this time I deleted the steps implying this connection : didn't work

Then finally I did it all over but I tried the alternative step "convert file using path" : didn't work

Now I need to warn all departments affected by this and wait for a solution from Microsoft.. Yay...