Thank you again. It is solved now by using on-prem jsreport using Azure Container App (following the tutorial from the docs). I was able to recreate the same issue when the container had 1CPU core and 2 GB memory. Bumping up to 4 cores and 8GB memory no longer has the issue, so it must be related to maxing out memory/cpu on the instances created in jsreportonline.

Thanks for the reply. Is there any way to configure the settings so that instances are not re-used? I'd prefer not to switch to on-prem since it will require more development/infra work and we're trying to get this issue resolved asap.

I'm using a batch process to call the the js reports API using .net to generate thousands of PDFs. It has rate limiting built-in to avoid hitting the concurrent request limits. After a few hundred PDFs are generated, I start seeing the following error in requests and they become more and more frequent until all requests are failing with the same error. The data for these requests is very similar, and running the request manually with the debugger does not hit the error. Any ideas for what might be happening?

I am using the cloud version of jsreports, with handlebars and chrome-pdf.

Protocol error (Page.printToPDF): Printing failed

ProtocolError: Protocol error (Page.printToPDF): Printing failed
at new Callback (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:62:35)
at CallbackRegistry.create (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:108:26)
at Connection._rawSend (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:224:26)
at CDPSessionImpl.send (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:433:78)
at CDPPage.createPDFStream (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:738:88)
at CDPPage.pdf (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:771:37)
at /app/node_modules/@jsreport/jsreport-chrome-pdf/lib/conversion.js:391:27
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /app/node_modules/@jsreport/jsreport-chrome-pdf/lib/conversion.js:432:22

Great that makes sense. Thanks.

Hello,

I have a use case to generate 6000 100-page PDFs (or 1200 500-page PDFs) from a template and dynamic data. I don't fully understand the pricing for JSReport Online which has 300k monthly credits as the GOLD subscription. (I assume this is the level we'd need for this type of request). The information under the subscriptions state "we won't interrupt the service when you reach the credit limits. Instead, you get a notification and another 50% credits which you can use to upgrade your subscription or optimize the traffic". Is this also true for the Gold tier? Once we reach the 300k monthly report credits, will the service continue to work, but we will be charged more?

Thank you

You're amazing thank you!

Thank you!
We'd like to use handlebars instead, but is it possible to do the same thing with handlebars?

Is it possible to include a jsrender condition in the JSON object which will then be evaluated at render time?
e.g. if I have this JSON object, with a dynamic condition, I want it to be evaluated in the "if" below to show or hide html depending on if it evaluates to true or false.
{
"age": 13,
"condition": "age > 18"
}

<div>
{{if condition}}
This text shows if age > 18
{{/if}}
</div>

In the above, this would obviously always evaluate as "truthy" because it is not evaluating the condition itself. Is it possible to interpret this as an expression to be evaluated by jsrender?