Reloads not according to schedule (Cloud Transfer Tool)

[SterreKapteijns]

Hello!

We transferred a customer to the Qlik Cloud using the Qlik Data Transfer Tool.  However, we have noticed that the reloads are not entirely according to the schedule. The customer needs reloads every 15 minutes, which is not possible when initalizing the reload schedule in the Qlik Cloud. However, we have now programmed in the data transfer tool that the data is reloaded 4 times per hour and that each reload triggers the reload of the dashboard.

However, we have seen in the reload history that these reloads of the dashboard do not happen on time and are sometimes even skipped. The logging of the Transfer Tool shows that the reloads of the data do take place on time. So it seems like it the problems are due to triggering the reload of the dashboard.

Perhaps there is some kind of queue? Meanwhile, there are no large amounts of data involved, so the amount of data does not differ much between 2 reloads. In addition, we have the impression that the reload history is incorrect, reloading sometimes takes minutes and the logging (4th column) indicates a few seconds.Reload historyAs you can see, the starting time differs every time. Although, the reloads of the data are scheduled at ..:10, ..:25, ...:40 and ...:55, such that the reloads of the dashboard are triggered at ..:15, ...:30, ...:45 and ...:00. 

Has anyone seen this before?

[Eugene_Sleator]

Hi @SterreKapteijns what you are describing appears to be working as designed.
As per the documentation;

 "Limitations and considerations

• If you have a high number of queued and executing data reload processes (and additional concurrent CPU and memory intensive processes), you might notice that some reload processes execute, in some cases, noticeably after their scheduled start time."

Reloading cloud apps 

Hope this helps!

[SterreKapteijns]

Hi @Eugene_Sleator,

Thanks for your response!

I'm aware of the limitation, however the amount of data does not differ much between these reloads.. so how can these reload times differ so much? 

And if this queue occurs, then why are some scheduled reloads skipped? If the queue gets to big? I would expect that all scheduled reloads are executed even if they are too late, but the limitation would imply that if the scheduled reload is delayed too much, it will not be executed anymore.

And why does the reload history say the reload time was "a few seconds" when in reality it was a couple of minutes?

Thanks in advance.