Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Optimizing Qlik Sense Reload Task Session Timeout

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Optimizing Qlik Sense Reload Task Session Timeout

Last Update:

Feb 15, 2022 8:08:26 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 4, 2019 9:38:55 PM

Qlik Sense Enterprise for Windows has a default “Task Session timeout“ of 1440 minutes (24 hours) and “Max retries” of 0.
 
“Task Session timeout“ is the maximum period of time before a task is aborted. When a task is started, a session is started by the manager scheduler and the task is performed by one of the worker schedulers. If the session times out, the manager scheduler forces the worker scheduler node to abort the task and remove the session.
 
Qlik Help: Creating reload tasks from tasks

 
Reload tasks performance is affected by many factors, which can make a reload significantly slower than anticipated.

  • Data source capacity
  • Data source process priority
  • Network bandwidth
  • Network path
  • Network congestion
  • Poor internet access

 
“Task Session timeout“ can be used to terminate a task that runs longer than expected, to avoid resource constraints with other parallel tasks. It is recommended to set “Task Session timeout“ lower than the task trigger interval, for example, lower than 60 minutes for hourly reload.
 
User-added image
 
Each failed task will rerun the number of times defined in “Max retries”, which has to be considered when defining “Task Session timeout“.

It is recommended to set “Task Session timeout“ and “Max retries” so that all retries with maximum timeout can be executed within the task trigger interval, for example, 3 retries of 19 minutes can be executed between each hourly reload.
 
User-added image
 
 
 
 

Labels (1)
Contributors
Version history
Last update:
‎2022-02-15 08:08 AM
Updated by: