Yes! That solved the issue, thank you.

In our PDF reports we're having an issue with repeating table headers. Our content of the page is dynamic, so we don't know how much content the page itself is taking. As a consequence, tables being placed below some dynamic content might be split over multiple pages (which is what we want). However, the issue is when the first 'actual data' tr doesn't fit on the first page, but the theaddoes, the thead is still being rendered, looking very silly. Is there any solution to prevent the rending of the thead. We can't do any calculations based on the content, since it's dynamic.

For an example:
https://playground.jsreport.net/w/anon/Nzw8LEHk

The issue itself has been solved by changing the way headers and footers are generated, using the merge whole documents functionality. No timeouts are happening now anymore.
As a follow-up question: are there ways to speed up the generation of the PDFs? At this moment we're running the Docker 2.3 jsReport engine in an Azure webapp (with 7GB of RAM, which should really suffice imho). PDF generation takes up to 10-14 seconds for 5 pages, using the same setup as in the first post.

Hi,

We're trying to generate a PDF with the first page(s) in landscape, followed by a set of pages in portrait.
When we add headers to the PDF, jsReport seems to timeout if the PDF is too large.
We're trying to leverage the power of jsreport-utils and PDFOperations (which is necessary anyway for the portrait vs landscape pages). Note that the header and footer are custom generated for landscape vs portrait margins and width.
Any suggestion for a better performing report would be welcome.
Currently the structure is the following:

- Portrait
-- Operations: [Merge header, merge footer]

- Landscape 
-- Operations: [Merge header, merge footer, append portrait]