Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

cdecluseau
New Contributor III

Task status explanation

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 !

8 Replies
btonthat
New Contributor

Re: Task status explanation

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.

mg_gsi_da
New Contributor III

Re: Task status explanation

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.

jaisoni_trp
Contributor II

Re: Task status explanation

We see Reset status when a task is in running state and scheduler services are restarted before the task completion.

s29124141
Contributor II

Re: Task status explanation

Hi jaikumarsoni‌, Do you know the reason for task to go to "Reset" status? We see some of our tasks went to Reset status.

martinsandin
New Contributor III

Re: Task status explanation

The Task will be set as Reset when:

  • The Scheduler Master starts and finds a Session in the Repository which is not running on any node
  • The Scheduler Master starts and finds a Session running on a node which is not found in the Repository
  • The Scheduler Master starts and finds the task in any non-terminal state but there is no Session. The terminal states are Aborted, FinishedSuccess, FinishedFail, Reset, Skipped, Error, and NeverStarted.

The task will be Skipped when it is triggered but:

  • The task is disabled
  • Reloads are disabled for the app
  • No appropriate Slave Scheduler can be found for that particular app
  • The Scheduler is not eligible to execute tasks (lacking license, not the master anymore, ...)

All these cases should be logged appropriately.

s29124141
Contributor II

Re: Task status explanation

Thanks Martin!

xufei123
Valued Contributor

Re: Task status explanation

Hi Martin,

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!

Fei

martinsandin
New Contributor III

Re: Task status explanation

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?