We sometimes encountered an issue when reloading a task, at night. In case of network connection lost, the task failed and finished. We set a max retries count to 3 but it didn't change anything. QlikSense server is not launching it again and
Does anybody encounter such a behavior ? Is the max retry parameter, used only in case of the initial task reload failure ?
Do you have a multi node setup for your environment or or are you running this on a single node?
It sounds to me like a common issue experienced with the setup of nodes.
What i would suggest, if you are using a single node setup: Look at your server environment for any background services running while the reload is executing.
Try introducing introducing things like "Sleep(5000), etc." into sections of your scripts running.
Point I am making: Your server seems to be overloaded with running services and there seems to be other things going on at the same time. Try to limit other processes .
Thanks for your answer. We are running a single node setup. The failure is due to lost of connection on the remote side (SAP Server over WAN link). Our QlikSense server is not overloaded. We thought the max retry feature would be the good ones to launch again a reload task in case of problem. Do you confirm it's not the case ?
In my setup, the tasks tries to restart automatically when it has failed due to an error like yours - max retry parameter is working fine here.
Hvae you concluded that multiple attempts are not made? Perhaps all tries failed?
You write: "Is the max retry parameter, used only in case of the initial task reload failure?" What do you mean by that? Is the failing task triggered from another task event and not being scheduled by time?
Hi! did you check the task logs in QMC, to see if retry attempts were made or if the failure was immediate? If the connection loss is temporary, increasing the interval between retries could help (though this is not directly configurable in QMC).
I've encountered again a failure for the same task, last week and this time, the retry was launched and successful (2nd time the task was started). So I confirm the configuration of the task was OK and I will increment the retry parameter.
