Buildship Puppeteer Timeout Issue
Hey there!
I am using a loop to generate ~200 pdfs using a slightly modified template for the HTML to PDF node.
This is using Buildship's internal puppeteer deployment if I am not misunderstanding (https://puppeteer.buildship.run/v1/pdf).
My PDFs are about 160Kb each when done. My problem is that after about ~100 iterations of the loop, my PDFs now become 39 bytes in my Supabase storage. Opening one of them as .txt instead of as .pdf shows the message "Navigation timeout of 30000 ms exceeded". Sometimes, the failed PDFs have the message "upstream request timeout" instead.
I tried many times to pinpoint the exact issue - this never happens when I generate about 30 PDFs. More than that, around 100, and any other PDFs generated in my loop are .txt with these error messages.
Could anyone check this and let me know if there is a simple fix to my problem? Is this issue coming from Buildship's server deployment of puppeteer ?
I am using a loop to generate ~200 pdfs using a slightly modified template for the HTML to PDF node.
This is using Buildship's internal puppeteer deployment if I am not misunderstanding (https://puppeteer.buildship.run/v1/pdf).
My PDFs are about 160Kb each when done. My problem is that after about ~100 iterations of the loop, my PDFs now become 39 bytes in my Supabase storage. Opening one of them as .txt instead of as .pdf shows the message "Navigation timeout of 30000 ms exceeded". Sometimes, the failed PDFs have the message "upstream request timeout" instead.
I tried many times to pinpoint the exact issue - this never happens when I generate about 30 PDFs. More than that, around 100, and any other PDFs generated in my loop are .txt with these error messages.
Could anyone check this and let me know if there is a simple fix to my problem? Is this issue coming from Buildship's server deployment of puppeteer ?
