"Issue with QlikSense Task Stuck in 'Triggered' State and System Unresponsiveness"

[qwebnm]

Dear Qlik Support Team,

I am writing to report an issue related to a QlikSense task and to inquire about the subsequent situation.

Initially, a task related to database connections transitioned to an "Aborted" state.

I have attached details of a previous inquiry regarding this situation for your reference.
Reference URL: https://community.qlik.com/t5/Connectivity-Data-Prep/QlikSense-HanaDB-ODBC-not-Connected-Issue/td-p/...

To address the issue, we attempted to restart the QlikSense service.
After restarting the service, QlikSense resumed normal operation, and the infinite loading issue also disappeared.

However, when initiating tasks, they enter a "Triggered" state but do not execute even after a significant amount of time, causing QlikSense to become unresponsive.

Qlik Sense Version: 13.51.22.

For your reference, I have attached an image that illustrates the issue.

Could you please provide some solutions or troubleshooting steps to resolve this problem?

Thank you for your assistance. 

[Alan_Slaughter]

Hi Qwebnm, Maybe this will help.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-reload-tasks-are-stuck-in-Trigger...

Qlik Sense reload tasks can get stuck in the "Triggered" state due to various reasons. One common cause is when the Qlik Sense Repository Service (QRS) is unable to communicate with the Qlik Sense Engine Service (QES) to execute the reload task. This can happen if the QES is overloaded or if there is a network issue between the QRS and QES.

To resolve this issue, you can try restarting the Qlik Sense services, particularly the QRS and QES. If the issue persists, you may need to investigate further by checking the log files for any errors or issues. Additionally, ensuring that the Qlik Sense environment has sufficient resources (CPU, memory, disk space) can help prevent such issues.