Hi, it depends. You can run the report with debug button in the toolbar and see what is the bottleneck.
In some cases, it is a custom script that you could be able to optimize.
But in some cases, the bottleneck is the "chrome-pdf" printing which is hard to optimize and there is no configuration in jsreport that could help. The only approach is to try to remove some CSS styles and step by step find out what is slowing down the most.
You can share your debug output here and we can see what you can do.
The issue is not related to js report. The problem was that we were storing the image in s3 and the s3 signed url had an expiry of 3 minutes so large reports wouldn't be able to access those urls. I just increased the expiry time and it solved the issue. Thanks anyway!
My issue seems very similar to https://forum.jsreport.net/topic/311/timeout-error-or-return-blank-sub-reports/10.
Here you have mentioned to increase the phantom js timeout.Where exactly you referred to increase it.Is it possible i can pass these configurations as part of payload of the post call in jsreports like