4.9.0 jsreport timeout issue

[kiakkai]

Recently switch jsreport version from 4.0.0 to 4.90 in azure app service.

The were a lot of time out issue such as :

"Error while executing html-to-xlsx recipe
(because) page.addScriptToEvaluateOnNewDocument timed out"

"Error: Timeout when waiting for profile blob to be fully persisted"

"warn+101387Report render failed (because) report timeout. Last profiler operation: (recipe) chrome-pdf."

Is this due to our enterprise licence has validated version for only 4.1.0?

[admin]

Do you use Azure Web App or Function App?
Do you deploy with docker container or code?

Try to add the following environment variable
chrome_launchOptions_args=--no-sandbox, --disable-dev-shm-usage, --disable-gpu

[kiakkai]

Thanks for your reply.

It is Azure web app and it uses Docker container.

After adding the environment variable "chrome_launchOptions_args=--no-sandbox, --disable-dev-shm-usage, --disable-gpu"into app setting, most of the timeout errors seem resolved except this one

Error while executing html-to-xlsx recipe
(because) timeout option must be a number
Error: timeout option must be a number
at module.exports (/app/node_modules/@jsreport/html-to-xlsx/lib/conversion.js:25:11)
at scriptHtmlToXlsxProcessing (/app/node_modules/@jsreport/jsreport-html-to-xlsx/lib/htmlToXlsxProcess.js:22:28)
at module.exports (/app/node_modules/@jsreport/jsreport-html-to-xlsx/lib/recipe.js:132:20)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async invokeRender (/app/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:93:5)
at async WorkerReporter._render (/app/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:148:7)
at async /app/node_modules/@jsreport/jsreport-core/lib/worker/reporter.js:233:24
at async processAndResponse (/app/node_modules/@jsreport/advanced-workers/lib/workerHandler.js:42:17)
wrapped by:
Error: Error while executing html-to-xlsx recipe
(because) timeout option must be a number
at module.exports (/app/node_modules/@jsreport/jsreport-core/lib/shared/createError.js:10:13)
at WorkerReporter.createError (/app/node_modules/@jsreport/jsreport-core/lib/shared/reporter.js:53:12)
at module.exports (/app/node_modules/@jsreport/jsreport-html-to-xlsx/lib/recipe.js:162:20)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async invokeRender (/app/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:93:5)
at async WorkerReporter._render (/app/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:148:7)
at async /app/node_modules/@jsreport/jsreport-core/lib/worker/reporter.js:233:24
at async processAndResponse (/app/node_modules/@jsreport/advanced-workers/lib/workerHandler.js:42:17)

However, I solved this by removing the environment variable called "CHROME_PDF_TIMEOUT=90000"

[admin]

Yes, this is an old config that broke it. Please keep it removed and use only reportTimeout root config.