
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tasks are terminated with the status "Reset" and the error "Execution session not saved in store, terminated". What do these errors mean?
Mar 3, 2022 5:26:51 AM
Jul 2, 2018 7:48:58 AM
After trying to run some tasks in Qlik Sense, the Qlik Management Console (QMC) shows them terminated with status "Reset" and the error "Execution session not saved in store, terminated". What does this mean?
Environments:
- Qlik Sense Enterprise on Windows , all versions
Repository or Scheduler services have shut down unexpectedly.
Resolution:
A task will be Reset when:
- The Manager Scheduler starts and finds a Session in the Repository which is not running on any node
- ThePrimary Scheduler starts and finds a Session running on a node that is not found in the Repository
- The Primary Scheduler 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.
And in the particular case of the message "Execution session not saved in store, terminated", this means Sense tried to load the repository data for a session but that the data wasn't there so the session was terminated. The corresponding log message might be more clear:
ExecutionSession not in the repository will be terminated.
The Scheduler will recover from this error and continue operations. The task it failed at will not be executed again but will run at the next scheduled time.
If necessary, please have your system administrators look into the behaviour of the Qlik Sense Services to investigate the reasons for the Scheduler or Repository services shutdown.

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
which logs to investigate to find out the root cause of this and where to find them?

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello @TusharDev_Qlik
Let me find out for you!

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
the issue got resolved as we found out the scheduler service got restarted as per daily backup procedure.
still the log locations would help us in future .
thank you.

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello @TusharDev_Qlik
The two log groups you need to review in this case are the Scheduler and Repository logs.
All the best,
Sonja