topic Re: V12.10 and queued reload in QlikView

V12.10 and queued reload

rennesia — Mon, 26 Jan 2026 18:19:17 GMT

Since upgrading from QlikView V12.0 to V12.10 almost every reload results in a queued status. Before upgrading, everything worked fine.

Is there a solution for this problem?

Re: V12.10 and queued reload

its_anandrjs — Wed, 23 Nov 2016 07:54:20 GMT

Please check the logs for the better ways.

Regards

Anand

Re: V12.10 and queued reload

rennesia — Wed, 23 Nov 2016 08:39:46 GMT

Attached you find (a part of) the performance log. In line 93 the server is restarted after upgrading to V12.10.
May be there is a designation to the cause of the queue in this file...

Re: V12.10 and queued reload

Thu, 24 Nov 2016 14:18:35 GMT

Does it stay in Queued state (then it indicates your system is overloaded) or is it just temporary until it enters Running state (then by design - a side-effect of the new load balancing feature)?

Have you enabled the load balancing feature?

Re: V12.10 and queued reload

rennesia — Thu, 24 Nov 2016 14:49:52 GMT

It stays in queued state continuously. After disable, enable and run a manual reload of document it comes directly in the queued state. The load balancing feature was not enabled.

I discussed this problem with our Qlik sales agent. He advised me to uninstall V12.10 and continue with V12.0SR5. At the moment I am busy with uninstalling and installing...
Thanks for your help Magnus!

Re: V12.10 and queued reload

fjn — Thu, 24 Nov 2016 15:40:31 GMT

On previous versions of QlikView “running” state included both tasks running and tasks that should start but couldn't due to overloaded system.

In QV12.10, tasks that cannot start due to overloaded system will be shown as “queued”, which will indicate that the system is overloaded.

Are you sure that your system was not overloaded? Long running tasks, many tasks, etc.

Have you been in contact with Qlik support regarding this problem?

/Fredrik

Re: V12.10 and queued reload

Peter_Cammaert — Thu, 24 Nov 2016 16:08:30 GMT

Ah, so the 'Queued' state appears when no free Reload Engine is available to launch the reload? Nice visual modification !

Re: V12.10 and queued reload

Fri, 25 Nov 2016 06:54:58 GMT

If you system is overloaded you should this in the LoadBalancer_[DATE].txt log file. Check for a row like this:

"The system is currently overloaded."

When not overloaded anymore, you should see "The system is not overloaded anymore." (this might take one minute until this is logged).

Re: V12.10 and queued reload

pauljohansson — Tue, 06 Dec 2016 12:46:24 GMT

Peter cammaert - hopefully not only visual.

To allow tasks to be queued rather than keep on trying getting a engine when there is non should be helpful in high load scenarios, at least, this is my hope. Can anyone confirm?

thanks in advance,

Paul

Re: V12.10 and queued reload

sarahallen1 — Thu, 08 Dec 2016 13:36:16 GMT

When we upgraded to v12.1 we noticed this, and realised that the setting for 'max concurrent reloads' had been reset to 1. We changed it back to 10 which was fine performance wise.

Might not be your issue though!

Re: V12.10 and queued reload

agigliotti — Thu, 30 Mar 2017 10:09:51 GMT

I'm facing the same issue.

I'm using the version 12.10.20000.0

I restarted the server and now the task status is waiting as expected.

It seemed a temporary problem.

Andrea

Re: V12.10 and queued reload

prees959 — Sat, 17 Nov 2018 10:14:01 GMT

@sarahallen1 wrote:
When we upgraded to v12.1 we noticed this, and realised that the setting for 'max concurrent reloads' had been reset to 1. We changed it back to 10 which was fine performance wise.

Might not be your issue though!

This solved it for us too!

Re: V12.10 and queued reload

Sonja_Bauernfeind — Mon, 19 Nov 2018 11:57:54 GMT

While not in reply to anyone specific here, I thought I'd put forward some troubleshooting steps and some information regarding task queuing. It might come in useful for other posters.

As mentioned already, 12.10 introduced a queue system. More about this can be read about here (000031318), along with some possible solutions to unexpected queuing right here (000042673). Should none of these apply, we have a few troubleshooting articles gathered together in this one (000024361).