What happens if app reload is started twice

[Jaeger]

I want to start reload of an app triggered by a file. The file is updated by ETL process every hour, after data is loaded successfully into DWH. The reload task is started hourly and inside a loop it loads the content of the trigger-file (txt) into a table and checks if the hour in the file data is the actual hour. If true then the data from DWH should get reloaded into the app.
1. Suppose the reload is started at 09:00 and the reload runs longer than 60 minutes.
At 10:00 the next reload starts although the first one has not finished yet.
What happens?
2. Suppose the reload is started at 09:00 but the trigger-file doesn't get updated because the ETL process needs more then 50 minutes to load the data into DWH. Is it possible to stop the Qlik Sense reload process from script without ending with an empty app (without data)?

[Nicole-Smith · Accepted solution]

I'm going to suggest a completely different process than what you currently have.

I would use QlikSenseTask as part of your ETL process and have the ETL process call the task at the end of its run.  That way the reload never starts and you don't end up with an empty report by trying to exit.  If you can't build the call to QlikSenseTask into the ETL process itself, maybe a windows scheduler task on a batch file that checks the log file and then does the call would do the trick.  Either way, the call is done outside of the reload of the app itself.

https://github.com/eapowertools/QlikSenseTask