Onedrive convert to PDF failure

(2) Share

Report

Posted on by CU29041724-0

I'm having an issue on a flow that has been working perfectly for the last year, and yesterday I'm having an issue with using Onedrive to convert word files to PDF. Using 'Convert File' (OneDrive for Business), I get this error:

    "message": "BadGateway",
    "innerError": {
      "status": 502,
      "message": "Timeout calling WRS where service endpoint Url=https://wordcs.osi.office365.us/document/export/pdf",
      "source": "api.connectorg.svc.ms"
 
I don't know why it stopped working or why it is getting a timeout error when contacting the API, does anyone know of a workaround or if this is a broader issue?
 
Here are some things I've tried to get it running (to no success):
• delete the operation node and re-add it
• delete the operation and use "Convert file using path"
• change the connection to another user & retry the two first options under the second user
 
Any suggestions?

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

BK-16121932-0 3 on at

Like (0)

Report

Also having the same issue starting today.

Was this reply helpful? Yes No
Suggested answer

Lagortinez 128 Super User 2025 Season 2 on at

Like (0)

Report

Hi there!

I just thested this connector on a dummy flow and it works like a charm:

Please keep in mind that the connector that you are using is under preview, meaning that it is not recommended for production. Instead, I would advise you to use another connector that will get you the job done and it is out of preview, as the Word Online (Business) Connector, and to be specific the step Convert Word Document to PDF.

With this connector, you get the same outcome but using a different way to achieve it:

If this post helped you, please click "Does this answer your question?" and give it a like to help others in the community find the answer too!

José Martínez Lago

Solution Architect | Dynamics 365 & Power Platform

Empowering low-code consultants to deliver high-impact solutions

🔗 Blog: thatsagoodquestion.info
🔗 LinkedIn: martinezlago

Was this reply helpful? Yes No
CU29041724-0 2 on at

Like (0)

Report

@Lagortinez

Word Online is a premium toolset I do not have access to, same with the Adobe toolset.

surely the answer can't be to pay for something then repurpose the entire flow that uses the function multiple times when it was previously working fine?

@BK-16121932-0

Nice to know I'm not alone in my struggles today

Was this reply helpful? Yes No
Lagortinez 128 Super User 2025 Season 2 on at

Like (0)

Report

@CU29041724-0 I checked and you are right... But the step that you are currently using is not behaving correctly. If you can't get a premium liscence, I can recommend that you start a free 30 day trial to keep your flow running, and then hopefully Microsoft will get the free standard connector fixed ASAP. In Europe this connector works like a charm, I would expect that they already have a team into this and is about to get fixed, so use this as a workaround. Moreover, open a Microsoft support ticket on your tenant, to get suppot and let them work. Other option would be using APIs directly, would that be a solution for you? Keep in mind that probably you would be sending your data outside Microsoft servers, and it would get processed in third party companies that might not be GDPR / Data Sensitivity compliant.

Let me know how can I further give you a helping hand 😉

If this post helped you, please click "Does this answer your question?" and give it a like to help others in the community find the answer too!

José Martínez Lago

Solution Architect | Dynamics 365 & Power Platform

Empowering low-code consultants to deliver high-impact solutions

🔗 Blog: thatsagoodquestion.info
🔗 LinkedIn: martinezlago

Was this reply helpful? Yes No