Pausing & Stopping QlikView Scripts

In our first video blog, we discuss how to gracefully pause and stop QlikView scripts, so that execution can be resumed later without existing script progress being lost!

I often found that when I would reload a QlikView application from my laptop, I would become tethered in place until the script finished. If I put my computer in Sleep mode, or disconnected it from the network (when the script required network access), the script would fail. Fortunately, I was able to win my freedom by implementing a simple trick, which I share in the following video:
 

 
Using this approach, you can safely put your computer into Sleep mode or disconnect from the network; when you wake it or reconnect to the network, the script can be un-paused and execution will resume normally! The supporting files used in the video are available for download here:
 
 
Please feel free to share in the comments section below your personal success stories using our approach! And, as always, happy Qliking!
This entry was posted in Tips & Tricks and tagged , , , . Bookmark the permalink.

4 Responses to Pausing & Stopping QlikView Scripts

  1. Small correction: the “SLEEP 200” statement in the video actually will cause a pause of 1/5 of a second, rather than 2 seconds. “SLEEP 2000” will cause a pause of 2 seconds. My apologies for the confusion.

  2. George says:

    Cool idea. Will come in use.

  3. Rahul says:

    Does it try after interval again and again till the execution completes?
    Example: We are extracting data from SAP , but due to some reasons (unknown), frequently SAP connector in qlik doesn’t work and it never extracts data form SAP, but this we notice after 8-10 hours. if i use Sleep command at the beginning of the script, will this work? i mean, will this be continues trying until qlik connects to SAP ?

    • Sounds like what you want is a loop combined with ErrorMode = 0. Possibly a very long loop with ENDFOR. I have scripts where random unexplained failures happen, but will succeed on retry. So I use these types of loops to try several times and check for success every time (usually by querying the number of rows in a table). If it didn’t succeed, try again. If it did, break out of the loop. You can certainly combine this type of thing with a sleep delay.

Leave a Reply to George Cancel reply

Your email address will not be published. Required fields are marked *

Notify via email when new comments are added

Blog Home
Archives