HTML to PDF node returns corrupted file
Hello together. I am using a workflow that takes html as an input and then uses the html to pdf node to generate a PDF file, that will then saved to a cloud storage. That Flow was wokring perfectly until 04.08.
When i used the workflow today the pdf links were generated but i can not open the pdf fieles in the cloud anymore. Apperently corrupted. When i check the node output it is empty. I tried to redo the node but codewise i looks like nothing chnaged in the node. Were there any changes to the https://puppeteer.buildship.run/v1/pdf rount that may cause such an issue?
3 Replies
It seems like you are experiencing an issue with the HTML to PDF conversion node in BuildShip. While I don't have specific information on changes to the
https://puppeteer.buildship.run/v1/pdf route, here are a few steps you can take to troubleshoot the issue:
1. Check Node Configuration: Ensure that all the inputs to the HTML to PDF node are correctly configured and that the HTML content being passed is valid.
2. Inspect HTML Content: Verify that the HTML content hasn't changed in a way that might cause issues during conversion. Sometimes, malformed HTML can lead to empty or corrupted PDF files.
3. Review Logs: Check the logs of the workflow execution to see if there are any errors or warnings that might give you a clue about what went wrong.
4. Test with Sample Data: Try using a simple HTML input to see if the node works with basic content. This can help determine if the issue is with the HTML content or the node itself.
5. Node Version: Ensure you are using the latest version of the node. Sometimes updates or changes in dependencies can cause unexpected issues.
6. Cloud Storage Configuration: Verify that the cloud storage configuration hasn't changed and that the storage service is functioning correctly.
If you have tried all the above steps and are still facing issues, it would be best to submit this issue via the in-app support button for further assistance from the BuildShip team.
For more information on the nodes you are using, you can refer to the following documentation pages:
- Generate EPUB Node
- WhatsApp Bot
If you need further assistance, please provide additional details, and I'll do my best to guide you.Generate EPUB Node 📖 – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
WhatsApp Bot – BuildShip
The WhatsApp Bot is a powerful trigger that allows you to connect and create a WhatsApp Bot using using WhatsApp Business Account by Meta.
Hey @S, Thanks for submitting a support request, We are checking on the intermittent failure of the puppeteer instance for the HTML to PDF node and will update you on the fix.
Also, on checking the recent logs of your shared workflow the pdf is generated successfully and is opening up with valid content. Sent you an email.
hey thanks for the response. yes we were able to fix the problem by readding the node - turns out that the "new" node does not return the FileBuffer anymore.
is there a way to see these kind of changes on the node when they happen? that was quite a breaking change for us. would be nice to knew in advance