topic Re: Task status explanation in Management & Governance

Task status explanation

_CD_ — Fri, 07 Jul 2017 08:34:37 GMT

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 !

Re: Task status explanation

Anonymous — Tue, 12 Sep 2017 04:52:05 GMT

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.

Re: Task status explanation

mg_gsi_da — Fri, 15 Sep 2017 05:40:21 GMT

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.

Re: Task status explanation

jaisoni_trp — Fri, 15 Sep 2017 18:48:51 GMT

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

Re: Task status explanation

s29124141 — Fri, 15 Dec 2017 20:31:23 GMT

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

Re: Task status explanation

martinsandin — Thu, 21 Dec 2017 12:32:23 GMT

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.

Re: Task status explanation

s29124141 — Fri, 22 Dec 2017 22:18:26 GMT

Thanks Martin!

Re: Task status explanation

NZFei — Mon, 12 Mar 2018 19:36:26 GMT

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

Re: Task status explanation

martinsandin — Tue, 13 Mar 2018 07:02:56 GMT

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?

Re: Task status explanation

TusharDev_Qlik — Wed, 02 Mar 2022 06:36:19 GMT

@martinsandin we are using QlikSense Nov 2020 version. we are getting below error for reset status.

Execution session found but the task is not running in slave scheduler. Session deleted.

we have this task scheduled to run daily and suddenly we are getting this error.

Re: Task status explanation

martinsandin — Wed, 02 Mar 2022 08:20:13 GMT

Hello @TusharDev_Qlik, I do not know why you're getting that error but maybe I can explain the message: it means that the database record (session) indicates there was a task running on an execution node but when asking the node in question the task isn't actually running there. The database record is therefore corrected by deleting the session.

This message would typically show up after a scheduler service restart.

Re: Task status explanation

TusharDev_Qlik — Thu, 03 Mar 2022 05:55:05 GMT

hi @martinsandin ,

thank you for the explanation , it was a scheduler service restart which caused the error.