web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Convert file using pat...
Power Automate
Answered

Convert file using path stopped working this weekend

(3) ShareShare
ReportReport
Posted on by 36
Hello,
 
I have a few flows that use Convert file using path to convert a docx file to PDF, and randomly over the weekend the connector stopped working.  It gives the following error:
 
 "status"406,
 "message""Conversion of this file to PDF is not supported. (cannotOpenFile / Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=UnsupportedMediaType)",
"source""api.connectorp.svc.ms"
 
Is anyone else having this problem?  I haven't made any changes when it started to give this error.
 
Thanks and I hope someone can help!
Categories:
I have the same question (1)
  • Vejai SH Profile Picture
    560 on at
     
    Did you verified the source file type for flow has error? 
     
    Thanks, 
    Vejai SH  
     
    Please mark as answer if my suggestion helps you.
  • JC-04081054-0 Profile Picture
    36 on at
     
    Not sure I understand your question, but the source file type (a .docx) does not have any problems.  I can open the file manually in my OneDrive with no problems. 
     
    My flow is an automated cloud that pulls a word docx from a folder, converts it to PDF, and places it in a different folder. 
     
    I even tested a previously processed DOCX that used this flow that gave no errors, and now it doesnt work and gives this error. 
     
    My suspicion is that either something at Microsoft is broken or possibly my company changed some policy that causes this connection to not work anymore.
     
    Thanks for the quick response though! Any other help would be greatly appreciated.
     
    Joe
  • Tomac Profile Picture
    4,138 Moderator on at
    The API that handles this request hasn't been updated since 2021, according to the documentation. Have you checked to see if there are related open or recently resolved issues in the Microsoft Fabric Service Status page?
  • JC-04081054-0 Profile Picture
    36 on at
     
    Thanks for the resource.  To be honest, Im quite a amateur with Power Automate, so I didnt even know where to look for outages or even how Microsofts systems all work in general.
     
    I checked the link you suggested, and it seemed like there was some type of outage for Europe (where I am) related to Azure Storage, but Im not sure thought if this is related to my problem.
     
    Anyway, I made a temporary solution for my flow and will continue to wait to see if there is a change or if someone on this forum has an idea of the problem.
     
    Thanks again for the help though!
     
    Joe
  • AS-04082320-0 Profile Picture
    4 on at
    Hi there,
     
    I am also having the same issue with one of my flows. It has been running perfectly fine for the last 2 months and have processed hundreds of .docx to pdf conversions.

    Today I get notified that one of my runs has failed.
    Upon checking:
     
    "body": {
            "status"406,
            "message""Conversion of this file to PDF is not supported.
    (cannotOpenFile / Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=UnsupportedMediaType)",
            "source""api.connectorp.svc.ms"
     
    I have had one run that occurred after this error that did work, so I'm not sure what's going on with this one in particular.
     
    Have checked the actions and all seems correct. Rerun does not resolve it either. 
     
    Suspect it could be an issue on Microsoft's end.
     
     
     
  • JC-04081054-0 Profile Picture
    36 on at
    To all,
     
    I realized something different when comparing a previous flow that worked and the same flow with the same docx that now doesnt.  In the "Headers" field, the content liength is drastically different.  Maybe the "Get file content" action is not working properly, in fact.
     
    Previously working Flow:
        "headers": {
            "Cache-Control""no-cache",
            "Pragma""no-cache",
            "ETag""\"{429A3516-C81C-480F-9101-7C87F73E1BB8},1\"",
            "x-ms-request-id""2dcc0a17-8a28-48bc-b1f9-c05874022b82",
            "x-ms-media-url""https://swedencentral1-mediap.svc.ms:443/transform/pdf?provider=spo&inputFormat=docx&cs=N2FiNzg2MmMtNGM1Ny00OTFlLThhNDUtZDUyYTdlMDIzOTgzfFNQTw&correlationId=ca76b6a1-104a-d000-7b0d-66ae47816fa9&docid=%7b1182462920%7d",
            "x-ms-file-name""MjAyNTA3MjlfSU1NU19FUVVJUE1FTlQucGRm",
            "X-AspNet-Version""4.0.30319",
            "X-Powered-By""ASP.NET",
            "x-ms-client-region""europe",
            "x-ms-flavor""Production",
            "X-Ms-Workflow-Resourcegroup-Name""selfhostingresourcegroup",
            "x-ms-workflow-subscription-id""Default-1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-environment-id""default-1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-tenant-id""1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-dlp-re""-|-",
            "x-ms-dlp-gu""-|-",
            "x-ms-dlp-ef""-|-/-|-|-",
            "Timing-Allow-Origin""*",
            "x-ms-apihub-cached-response""true",
            "x-ms-apihub-obo""false",
            "Date""Tue, 29 Jul 2025 08:15:03 GMT",
            "Content-Length""371159",
            "Content-Type""application/pdf",
            "Expires""-1"
        },
     
     
     
    Same Flow, Same Document, not working:
     "headers": {
            "Cache-Control""no-cache",
            "Pragma""no-cache",
            "Transfer-Encoding""chunked",
            "x-ms-request-id""d3d308c9-1a68-4e0e-ba17-12992ef81ad1",
            "x-ms-media-url""https://swedencentral1-mediap.svc.ms:443/transform/pdf?provider=spo&inputFormat=docx&cs=N2FiNzg2MmMtNGM1Ny00OTFlLThhNDUtZDUyYTdlMDIzOTgzfFNQTw&correlationId=8cb4b8a1-20f8-d000-7b0d-6ed4cd0b57cc&docid=%7b1080810302%7d",
            "X-AspNet-Version""4.0.30319",
            "X-Powered-By""ASP.NET",
            "x-ms-client-region""europe",
            "x-ms-flavor""Production",
            "X-Ms-Workflow-Resourcegroup-Name""selfhostingresourcegroup",
            "x-ms-workflow-subscription-id""Default-1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-environment-id""default-1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-tenant-id""1f8914ab-f16e-4f30-80af-37eaf4081bf2",
            "x-ms-dlp-re""-|-",
            "x-ms-dlp-gu""-|-",
            "x-ms-dlp-ef""-|-/-|-|-",
            "Timing-Allow-Origin""*",
            "x-ms-apihub-cached-response""true",
            "x-ms-apihub-obo""false",
            "Date""Tue, 05 Aug 2025 07:22:13 GMT",
            "Content-Type""application/json",
            "Content-Length""264",
            "Expires""-1"
        },
  • Verified answer
    Tomac Profile Picture
    4,138 Moderator on at
     
    Looks like something went sideways with the Sensitivity Labels over the last week. You'll need to do the following:
    1. Open the document in your web browser (Office Online editing)
    2. Change the Sensitivity Label
    3. Save the document and wait for the Save to complete
    4. Change the Sensitivity Label back
    5. Save the document again
    After that your flows should work. Thanks go to this thread for finding the solution.
  • JC-04081054-0 Profile Picture
    36 on at
     
    Ah wow great.  Thank you for finding that.  There is a problem though, that my document says "Sensitivity not supported".  So there are no sensitivity labels.
     
    I have forgot to mention that my document has restricted editing sections and content control, so its possible that my problem is related to this problem, although its not the same problem others are experiencing.
     
    Its good to know that Microsoft is working on it, so I will see if they fix it in a few days.
     
    Thanks again for the help!
     
     
  • JC-04081054-0 Profile Picture
    36 on at
     
    Quick note:  I tried a test word document I just created with no restrictions and it works now. 
     
    So its definitely related.
     
    Thanks again!
  • FH-05081307-0 Profile Picture
    3 on at
    Hello,
     
    The verified answer does not work for me and neither do the different suggestions in the other thread (Solved: Error occurs in Microsoft Word Action - Convert Word Document to PDF). 
     
    One member in that thread stated Microsoft is aware of the issue. Just leaving a message here for the other people who have no luck changing the sensitivity label.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 386

#2
Valantis Profile Picture

Valantis 342

#3
Haque Profile Picture

Haque 336

Last 30 days Overall leaderboard