Power Automate Flow - Convert File to PDF not working

[HaveeLand]

July 10, 2024

Hello All,

Short Version of issue: 

• Flow runs successfully.
• Flow creates an .html file
• Flow converts .html file to .pdf
• Flow creates a .pdf file using the "body" of the conversion from .html to .pdf
• 2 files are created in my OneDrive account.
  • .html file opens perfectly (1st File)
  • .pdf file Does Not open (2nd File)

Longer version if you need more details.

It appears that a few years ago, other people were having a similar issue across multiple users and the problem eventually was corrected after a few days.  Hopefully the issue is only on my account and not a global one like last time.

Here is my issue:  I have a flow that is Manually triggered and I write some basic "Hello World" HTML code in a "Compose" function. 

I use {Create file} and I am able to create an .html file in my OneDrive folder and the document opens in any browser I use. 

HOWEVER, when I use the {Convert file} for a PDF target type, using the html file from above, the flow runs successfully, however in the raw output file, it shows a "Content-Length": "0" (zero) value. 

Which then is considered the {body} and when I use it in the {Create file} under the File Content to convert the file to PDF. It generates a PDF file with a value of 1kb and I get an error message that the PDF file can NOT be opened.

So, my TEST Flow creates 2 files.  An .html file that works as intended and it also creates a .pdf file that I am NOT able to open.

And yes... as of this afternoon 7/10/24, everything was working and converting properly.

So, hopefully I added all of the information needed to solve the issue and you can direct me to a solution.

Thank you all in advance

-Javi

[Sayan]

Hey @mpfeng for my case It is accepting the file path as input.

Because there is also, we can browse File using it.

Thanks,

Sayan Patra

RPA Developer

[mpfeng]

Hi @Sayan Thanks for providing us a suggestion of a workaround. Yes, I think that can be applied when the file already exists and the name is already known: then, you can select it by clicking in the root icon and navigate until you find the file. On the other hand, when the file is created dynamically by the flow with a different name each time the flow is executed, then I think that approach cannot be used. Anyways, as reported by others here, the issue is fixed.