Hi all !
On the QMC/task section, the status can contains some values. We can show these values here https://help.qlik.com/en-US/sense/June2017/Subsystems/ManagementConsole/Content/tasks-overview.htm.
It's not really detailed. We have the possible values but no explanation why we can get them.
And the most questionable one for me is "Reset". Why a reload could finish in a Reset status. I don't understand the "i"nformation on the task.
I also question me on "Queued" and "Skipped".
As we can configure a "Max concurrent reloads" for the scheduler service, I understand that a task coul be in "Qeued" status.
But "Skipped" ??
Thanks for your help !
Yes, I have same question about the ...Reset. Why a task was running and finished with a status "...Reset". What does it mean? I found your question and it is a dead end for me.
For skipped I may have a explanation. Usually this is the status for tasks which are disabled.
But we have a situation today where some of our tasks went to status reset. I have no idea what went wrong but the reload did not take place for some but not all with the same status.
The Task will be set as Reset when:
The task will be Skipped when it is triggered but:
All these cases should be logged appropriately.
Could you please explain when and why the reload tasks are in queued status?
We are having the problem that only one reload tasks at a time but it is in queued status so don't know why and how to fix it.
Thank you so much!
When a task is triggered the Master Scheduler will find all Slave Schedulers who can execute it and send the task to the one with the lowest CPU load. If the Slave Scheduler is already at the maximum number of allowed simultaneous reloads (i.e. engine connections) it will queue the task until such a time that there is a free engine connection.
May I ask which version of Sense you are using as well as number of simultaneous reloads (engine connections) you allow for you Slave Scheduler?