Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I was making changes to the script of an app currently in development; there is no associated task being published.
The issue is that it has gotten stuck, and now, no matter how many times I run the script, it always says "in progress." It’s been like this for two hours, the app normally takes just two minutes to run the script. Has this happened to anyone else?
Usually, in cases like this, you’d check the tasks to investigate, but here there is no associated task. Any idea where I should look?
Thanks in advance,
Isaac
Hi
Yes, this can happen in Qlik Sense even when there is no associated reload task.
Check QMC → Apps and confirm no reload is actually running.
Check Engine and Repository logs around the time the reload got stuck.
Verify Engine server CPU, RAM, disk space, and active sessions/reloads.
If still stuck, restart the relevant Qlik Sense Engine/Repository service during a maintenance window and retry.
Hi @IsaacC
Any recent changes to the environment? Upgrade? Patch?
Check the script logs:
Get the AppID from the browser URL and then check C:\ProgramData\Qlik\Sense\Log\Script\.
You should be able to find related information in the engine logs as well. The default path is C:\ProgramData\Qlik\Sense\Log\Engine\Trace<node>_System_Engine.txt
You can also try to duplicate the app from the hub to confirm it's not a file lock.
I hope that helps.
Regards,
Eduardo Monteiro - Senior Support Engineer @ IPC Global
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hi
Yes, this can happen in Qlik Sense even when there is no associated reload task.
Check QMC → Apps and confirm no reload is actually running.
Check Engine and Repository logs around the time the reload got stuck.
Verify Engine server CPU, RAM, disk space, and active sessions/reloads.
If still stuck, restart the relevant Qlik Sense Engine/Repository service during a maintenance window and retry.
@Eduardo_Monteiro @Chanty4u thanks guys, finally after 3 hours, the script runs again without any issue. I must say that I haven't taken any action.