hi! in this case the best would be that you also do the header, footer part using pdf-utils, you need this because the native chrome header/footer has no way to be aware that you are doing a parallel generation, you need to do the header, footer using pdf-utils because with that you will be able to take into account some logic to print the correct numbers, basically, you need to also render the header/footer in your after render script and merge it passing the correct page number and total.

if you have some doubts about how to do it, you can always prepare a basic demo (with some very basic data that just replicate producing the same pages count) on the playground and then share it here, then we can update it.. checking real code is the best way we can guide you.

hi! hmm your code looks correct i've tried to replicate the same here and it works. maybe you can try it to replicate in the playground also and share the link back here

hmm it seems it is not possible at this moment, i'm opening an issue to implement this, you can keep track of the progress here

hi! hmm i'm not sure what can be the issue, but in any case this does not look like an issue with jsreport itself, maybe the nodemailer changed its api a bit since the post was made, you probably need to check the nodemailer docs and verify that the options you are using are the correct ones.

@izelt sorry for the long wait. FYI i have sent you email with some notes about the problem and a workaround for your case.

not yet, it is added to my work queue so i will get to it soon, sorry for the wait

there was an incident in the server that handles the playground, it should be fixed now. sorry for the inconveniences

@izelt i have received the email with the details, we will check the problem and reply here with some news when we find the issue. thanks for the help

I have included our config file in the zip (and also the start-up script, as it installs some specific npm modules into the docker container) - where should I email it to?

thanks, this will really help to verify the problem. you can send it to bjrmatos@gmail.com

hi! hmm i think this problem is related to a folders migration logic we run when you update to any version > 2.3.0.

are you storing your templates using fs-store?

this is a similar topic https://forum.jsreport.net/topic/1262/error-because-of-folder-shortid/6 in which i ask for some help to reproduce the issue so we can fix it, maybe you can help us sharing your original entities (the entities previous the jsreport upgrade to 2.4.0), you can share a zip of your data folder and your config file privately via email if you want to help us to fix this. unfourtunately this is the best way for us to replicate the problem, since we are not able to replicate the same issue, so it probably means that it is only affecting some specific migrations and your case will help to verify this.

quote from the other topic:

are you able to replicate the issue every time you upgrade the jsreport? i mean, if you go back to your previous jsreport/jsreport:2.0.0-full image with the same data folder that you have at that time, and then try to upgrade to jsreport/jsreport:2.6.1-full, does the issue continues to happen every time? if this is something you can reproduce every time you try to migrate from jsreport/jsreport:2.0.0-full to jsreport/jsreport:2.6.1-full then best will be that you share with us the data folder that you have on jsreport/jsreport:2.0.0-full so we can inspect what is happening, since the addition of folders entities to jsreport (v2.3.0) there is a migration step that we run at jsreport startup that tries to migrate entities to folders, it can be the case that this migration is causing this issue by duplicating the shortid, however we never saw this before.