Qlik Sense reload tasks are stuck in Triggered state in the Qlik Sense Management Console

[Rakesh_HB]

A Qlik Sense reload task is stuck in the Triggered state. All services are otherwise running and other tasks are executing and finishing correctly. 

Reviewing the Qlik Sense Scheduler logs shows:

Execution session found during resume is not running in any slave scheduler and will be deleted

and/or

Unexpected exception in Delete for Entity ExecutionSession with Id < >

Resolution

1. Change the scheduler settings in Qlik Management Console to Manager and Worker (Not necessary in Single node)
2. Stop all the Qlik Sense Services except the Repository database service
3. Make a backup of the Repository database: How to backup PostgreSQL database in Qlik Sense.
4. Locate pgAdmin or install it. Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinti...
5. Open and Log in to PGAdmin
6. Login to (newly added) Qlik Sense Server in PGAdmin
7. Expand QSR Database
8. Find and Open the ExecutionSessions table
   
   
   
   
9. Right Click - View/Edit Data - All Rows in the ExecutionSessions table or Open Query Tool and Run the below query:
   

   SELECT 
     "ExecutionSessions"."ID", 
     "ExecutionSessions"."AbortAt", 
     "ExecutionSessions"."Retries", 
     "ExecutionSessions"."AbortReason", 
     "ExecutionSessions"."User", 
     "ExecutionSessions"."CreatedDate", 
     "ExecutionSessions"."ModifiedDate", 
     "ExecutionSessions"."SyncDate", 
     "ExecutionSessions"."ModifiedByUserName", 
     "ExecutionSessions"."App_ID", 
     "ExecutionSessions"."ExecutingNode_ID", 
     "ExecutionSessions"."ExecutionResult_ID", 
     "ExecutionSessions"."ReloadTask_ID", 
     "ExecutionSessions"."UserSyncTask_ID", 
     "ExecutionSessions"."ExternalProgramTask_ID"
   FROM 
     public."ExecutionSessions";

10. If you get any errors as below, delete that entry and Run the query again.
    

    ERROR:  syntax error at or near ""ExecutionSessions""
    LINE 1:   "ExecutionSessions"."SyncDate", 
              ^
    SQL state: 42601
    Character: 3

11. Wipe the data from the ExecutionSessions table. See SQL statements below.
    
    Please note that this will need to be a hard deletion from the table and not soft deletion. For this, run the below Query;
    

    DELETE 
    FROM 
    public."ExecutionSessions";​

12. Restart the QlikSense Server ( full reboot ).
13. After the reboot, start the Qlik Sense services (if not already started) and try running the tasks again.

Cause

Corruption may occur due to:

1. A row that is incomplete ( blank values ) in the ExecutionSessions table data
2. ID reference to a task that does not exist anymore
3. Entries flagged as incomplete that interfere with the execution queue ( block the next tasks )
4. Entries with IDs that already exist in the table, and new entries with the same ID will cause an error and abort the execution

This can look like this in the repository database:

Environment

• Qlik Sense Enterprise on Windows All the versions

[gandalfgray]

We had this issue in our multi node Nov 2022 environment, following an issue where the worker node stopped functioning and was replaced with a new.

For us the solution was a bit simpler:

We restarted the Repository service on the central node, which first failed because it could not stop the Scheduler service. After killing the Scheduler.exe process we could restart the Repository service and all services. This fixed the issue and the tasks status were changed to "Reset"