I've tried 3.13, 3.11.0, 3.1.1 and in all cases, it makes a margin just for the first page which is expected.

Btw the page margin has this css

@page {
      margin-top: 5cm;      
 }

Your problems could be caused by a different version of chrome which may apply some specific things differently. Unfortunately, there is nothing we can do about it. jsreport just uses the latest chrome as it is without tweaking it.

After I downgraded the jsReport on production from 3.13.0 to 3.1.1, the overlapping issue disappeared.

I am not aware of anything that could cause such change.

The jsReport version is 3.13.0. Does it seem right to you?

Your template doesn't set top margin. This means the content of the main template will start at the top and merged templates like headers will likely overlap. Try to set a top margin explicitly and check the result.

Please share jsreport output logs.
You can find it in stdout or in the app folder logs/reporter.log

Thanks. It looks like you just forgot to set the top margin for the main template. Could you check it?

The component can add a script that breaks the rest of the js on the page...
Would you be able to provide a playground demo replicating the issue?

What kind of header is that? Is it a header template merged using pdf utils?

it does not generate this log file

I'm not sure what you are asking. The timeout could occur because you didn't fire the printing trigger. Maybe because of some js errors on your page.

Your report seems to use that importStylesheet but you didn't provide it in the template.helpers prop.

If you want to run with full profiling a particular request, you can use the following button

If you want to switch to "full profiling" all reports using studio, use the following

You can also manage the default mode using server config https://jsreport.net/learn/configuration
So for example open jsreport.config.json and add there a value

{ 
   ...
  "profiler": { "defaultMode": "full" } 
}

You can send the same in the API call.
https://jsreport.net/learn/scripts#api