Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Script Execution Progress

Has anyone else noticed that the Scrip Execution Progress does not display until it is completed or there is an error.  Its something silly but its super frustrating because I never know if it is hung up or still chugging along.

I have had an extract script running for about 5 minutes and the image shows 'Connected' with 00:00:00 time elapsed!

4 Replies
Not applicable
Author

Hi Katie,

try using the trace command with the following syntax in some parts of your script.

Trace ---- verification text ------;

so you can track the progress of your job


m2r4miller
Contributor III
Contributor III

I have the same issue - doesn't matter if I am loading from QVDs or through an ODBC connection. Sometimes the progress will display correctly, sometimes not.

This began after I installed SR9 of QV 11.2 (I jumped from 11.2 SR5 to 11.2 SR9).

Currently I'm running 11.20.12664.0 SR9 64-bit Edition.

I put TRACE in my scripts and that will not show either - the progress window just sits there empty until it finally disappears when the script is finished.

If I check the "Keep progress open after reload" option under User Preferences, then I will get a display once the script has completed - showing all my TRACE statements, and record loads:script execution.JPG

Sometimes it works, sometimes it doesn't - quite frustrating at times.

haymarketpaul
Creator III
Creator III

yes same issue here

m2r4miller
Contributor III
Contributor III

*** UPDATE ***

I have upgraded to QV 12, currently running QV 12.0.20001 SR1 and the issue remains still.

I have discovered that if I reload from within the script editor, then 99% of the time the Script Execution Progress dialog will work correctly, and show all the progress throughout the load.

It is still frustratingly inconsistent, however and hopefully will be addressed in a SR soon.