How to set Default Report Timeout in NPrinting

[bnaveen]

Hi,

Is there a default setting/configuration to abort the NPrinting report request if it is running for a long time?

Sometimes requests are taking a really long time for months and unless we manually check and abort, we are not able to stop them. If there is a way to fail a report if not processed after X minutes/hours that would really help.

I couldn't find anything in the documentation. Appreciate any help on this.

Qlik NPrinting @QlikNPrintingUpdates @nprinting 

Thanks

[Frank_S]

ps: I am also asking R&D if there are any minimum value settings for :

scheduler.config:

=========================================
Scheduler options
=========================================
-->
<add key="report-timeout-minutes" value="1" />
<add key="generate-cache-timeout-minutes" value="1" />
<add key="ondemand-timeout-minutes" value="2" />

[Frank_S · Accepted solution]

R&D has provided a deep-detailed answer in which I will summarize here.

While there are no lower limits, these timeout settings are essentially present to handle very specific scenarios. Mainly incrementing the default timeouts in order to allow NPrinting, Qlik Sense or QlikView servers that might be overburdened temporarily, to complete NPrinting executions (on demand, report task, connection processing etc). 

*The primary intention of these settings therefore is not to cause a 'fail' or 'abort' of any NPrinting executions but to allow valid, long running execution to complete.*

In a nutshell, lowering these values is not suggested. Increasing them will allow NPrinting reports to generate if the system is temporarily overburdened or if they simply require more time to complete. 

However, if you need to force the abort of a report execution, this can be managed by the end-user or by the NPrinting administrator as per the following articles.

• Managing On-Demand requests
• Task executions
• Generating On-Demand reports in QlikView AccessPoint
• Publishing a complex report from a Qlik Sense app

Now if your systems are consistently overburdened, then it is advised to setup performance monitoring of each of your Qlik Server's CPU, RAM, and Disk usage. If any or all are consistently maxing out, it is recommended to add system resources to accommodate any increased load on your existing servers.

You may also consider improving the performance of your report itself which may include:

• avoiding heavy use of cycles
• ensure to carefully follow filter rules
• ensuring there are no calculated dimensions in your source QVW or QVF
• reduce your QVW or QVF for NPrinting reporting purposes
• remove unneeded objects from your reporting QVW or QVF
• remove the unsupported object from your QVW or QVF

Should you need assistance with more detailed requirements in configuring your Qlik Architecture, you may wish to connect with your Qlik Account or Partner manager to leverage the vast experience of our professional services team.

Kind regards...

[bmulvanyw]

Thank you for the detailed responses. Do you know what the default value is for the timeouts? The setting are currently commented out in our config, that would be great to know.

Just some background, my reason for reaching out is because we had a scenario where reports that would complete after a minute or so were running for 9+ hours which we eventually manually aborted.  Actually no reports executing on that server completed during this time.

If there is already a default set for the timeout settings even with them commented, then I agree we should probably leave them as is as it might not even impact the scenario we had run into.

[Frank_S]

No worries!

Here you go.

  =========================================
 Scheduler options
 =========================================
 -->
 <!-- <add key="report-timeout-minutes" value="720" /> -->
 <!-- <add key="generate-cache-timeout-minutes" value="720" /> -->
 <!-- <add key="ondemand-timeout-minutes" value="120" /> -->