if multiple task are scheduled at the same time than due to lack of memory this might have happen.....say suppose if their are 10 jobs get trigger at the same time and qlikview doesn't have enough memory then it will end up in failure of few task...try to change the timing like 2:15 and test it for couple of days
But changing the time would help in this case can't agree to that.
after analyzing - there aren't many jobs ran simultaneously at the same time (which will be a matter of throttle resource), that being said. The job never ran because the scheduled time didn't kick off.
Attaching the task and also under Started/scheduled section where it show the next planned refresh shows up as "Not scheduled" for some reason.
So we happened to play this in different ways to see whether the solution is a more stable.
Initially we have deleted the whole task and recreated the task again with the same trigger. Process ran for couple of days then the problem persisted again. As we thought may be the qvpr xml files got corrupted.
Now this time we deleted the trigger and recreate and before we ran we have restarted the Qlik services which is running as expected for a day so far. will be monitoring the same for the next few days.
If the current situation fails Qlik has suggested to change the chunk size from our current value '50' to '20' and restart the services back again.
But curious to see if anyone encountered the same issue ever before and how they figured out a solution to this?