Power Platform Community Forum Thread Details

Subject: Word Online "Convert Document to PDF" returns 404 Not Found in flat SharePoint folder

Body:
I am seeking help with a persistent "Not Found" error in a Power Automate flow. I am currently testing a simple conversion in a flat directory (no sub-folders) before moving to a more complex nested structure, but the Word Online connector fails to resolve the file.

The Setup:

Trigger: Manual button with a text input for batch naming.
Get files (properties only): Pointed at a specific test folder containing two files: one .docx and one .pdf.
Filter Query: FSObjType eq 0 (used to ensure only files enter the loop).
Apply to each: Iterates through the outputs of the "Get files" step.
Condition: A check to ensure FilenameWithExtension ends with .docx.
Action: "Convert Word Document to PDF" (Word Online Business connector).

The Problem:
The "Get files" step successfully identifies the target .docx file (verified in the execution logs). However, the "Convert Word Document to PDF" action fails with a "Not Found" error. Even though there are no sub-folders in this test, the connector cannot locate the document.

Technical Details & Attempted Fixes:

Pathing: I have tried passing the {Identifier} chip, the ID (integer), and the {FullPath}.
Formatting: I have tried prepending a leading forward slash to the path using concat('/', items('Apply_to_each')?['{FullPath}']).
Raw Input Inspection: The raw inputs for the failed "Convert" action show a valid absolute path: "/TestFolder/TargetFile.docx".
Loop Behavior: The "Get files" output confirms only the .docx is being passed to the conversion branch due to the filters, yet the 404 persists.
Connections: I have deleted and recreated the Word Online Business connection and the action card to refresh the metadata.

Despite the path being correct and the file being visible to the SharePoint connector in the preceding step, the Word Online connector refuses to resolve it. Has anyone encountered this where the Word Online API fails on a file that the SharePoint "Get files" action clearly sees in a standard flat folder?

Categories:

Building flows