Skip to main content Skip to complementary content

Start task

Procedure

Qlik Sense performs the following procedure:

  1. A request is sent to the Qlik Sense Repository Service (QRS).
  2. The manager Qlik Sense Scheduler Service (QSS) on the central node communicates with each worker QSS to see which ones are available to perform the task.
  3. The task is given to the currently available worker QSS with the least load according to the load balance rules.

Success

In case of success, log entries are written in the following files throughout the procedure:

  • <MachineName>_AuditActivity_Scheduler.txt
  • <MachineName>_AuditActivity_Repository.txt

Errors

Task not found

Task not found error
Description Command=Start task;Result=5;ResultText=Error: Failed
Message Task not found
Action

Try the following measures:

  • If the repository database is accessible, search the database for the task.
  • Check if the task has been successfully synchronized to the rim nodes.
  • Create a new, identical task and see if it works.

Scheduler is not licensed

Scheduler is not licensed error
Description Command=Start task;Result=10;ResultText=Error: Failed
Message Scheduler is not licensed. Not allowed to run Tasks
Action Provide a valid Qlik Sense license.

Scheduler is not Manager

Scheduler is not Manager error
Description Command=Start task;Result=15;ResultText=Error: Failed
Message Scheduler is not Manager. Not allowed to run Tasks
Action Make sure that the QSS on the central node is “Manager” or “Manager and Worker”.

Found active session for Task

Found active session for Task error
Description Command=Start task;Result=20;ResultText=Error: Failed
Message Found active session for Task. Task not started
Action

Try the following measures:

  • Wait until the task has completed.
  • Stop the task.
  • Restart the QSS.

Task disabled

Task disabled error
Description Command=Start task;Result=25;ResultText=Error: Failed
Message Task disabled
Action

Enable the task.

TaskExecutionSession already exists

TaskExecutionSession already exists error
Description Command=Start task;Result=30;ResultText=Error: Failed
Message TaskExecutionSession already exists for App <App.Name>
Action

Try the following measures:

  • Wait until the task that is reloading the app has completed.
  • Stop the task that is reloading the app.
  • Restart the QSS.

No worker nodes found to execute Task

No worker nodes found to execute Task error
Description Command=Start task;Result=40;ResultText=Error: Failed
Message No worker-nodes found to execute Task: <Task.Name>
Action

Proceed as follows:

  1. Check the status of the worker nodes to determine if they can perform a reload.
  2. Check that the app to reload exists on the worker nodes.

Unable to create TaskExecutionSession

Unable to create TaskExecutionSession error
Description Command=Start task;Result=45;ResultText=Error: Failed
Message Unable to create TaskExecutionSession
Action

Restart the QSS.

Unexpected exception when starting task

Unexpected exception when starting task error
Description Command=Start task;Result=50;ResultText=Error: Failed
Message Unexpected exception when starting task. Exception message: <Exception.Message>
Action

Restart the QSS.

Unexpected exception when trying to start task

Unexpected exception when trying to start task error
Description Command=Start task;Result=55;ResultText=Error: Failed
Message Unexpected exception when trying to start task. Exception message: <Exception.Message>
Action

Restart the QSS.

Max number of retries reached for task

Max number of retries reached for task error
Description Command=Start task;Result=80;ResultText=Error: Failed
Message Max number of retries (<Amount>) reached for task (id/name) <Task.ID>/<Task.Name>
Action

Restart the QSS.

Not possible to initiate retry

Not possible to initiate retry error
Description Command=Start task;Result=90;ResultText=Error: Failed
Message Not possible to initiate retry. TaskExecutionSession is null
Action

Restart the QSS.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!