Qlik SaaS App Reloads

[stevejoyce]

What is the advised best way to schedule reloading of applications in Qlik SaaS?  I know apps can be set on a "schedule reload" or use an Automation.  Is it true Automations cannot be shared and so can only be manually kicked off by the person who owns it?

Ideally I am just looking for the on-premise qmc view for tasks, where I can chain some apps, see status, reload from that same view if need.

I ditched "schedule reload" because it was too basic:  ,couldn't edit, couldn't chain reloads, can't abort, status was buried, couldn't start manually.

I setup Automations for each of my apps, which seems to be doing a good job, but i realized that Automations are only available to me as I created them which is not good.

[Vinay_B]

Hi @stevejoyce 

As you pointed out, Automation cannot be shared with anyone else. Only the user who created Automation will be able to run it. 

Have you tried Qlik CLI? You can schedule reloads from there as well and can be managed by a team.

 https://community.qlik.com/t5/Knowledge/Qlik-CLI-support-and-compatibility/ta-p/1735424 

I hope this helps!

[stevejoyce]

Thanks @Vinay_B .  I don't see the ideal approach for reloading apps to be from script files.  Is this the closest approach to QMC in either qlikview or qliksense on-prem? ☹️

[squeakie_pig · Accepted solution]

Hi.  I would recommend Automations, especially if reloads need triggers from the completion of a prior reload.  Automations can be scheduled so you don't need to rely on the creator running it.  Plus, you can change the owner in QMC so if someone needed to make changes or updates to it, it is just as easily done as any other app. 

The main issue we have experienced is there a non-changable parameter where an automation can only run for an hour.  So if you are reloading a lot of apps and some of them take a while - might be best to plan it a bit more than sholve all reloads into one.  It's like Batman says "Failing to plan is planning to fail." Automations can also be triggered by the end of another automation.

This is a new feature so I assume qlik will be investing heavily in it and expect things like 'only the creator being able to see it' to possibly be different in the future.

[PietMichielRappelet]

Hi

Appreciating your feedback here! We are working on many improvements and additional features and I would suggest submitting your improvement ideas in our ideation page: https://community.qlik.com/t5/Suggest-an-Idea/idb-p/qlik-ideas

on this specific topic, 

• you can 'fire and forget' reloads with the setting "start reload and continue", allowing to start many reloads within the 1hour limit.

• If you have 'chained' reloads, you can use the approach shared on the following link. In summary, you'll need an orchestration place to keep track of your reloads and use different automations to check the reload status and start subsequent actions:  https://community.qlik.com/t5/Knowledge/How-to-build-long-running-task-chains-in-Qlik-Application/ta... 

hope this helps! 

[stevejoyce]

Agreed on the change ownership.  I think this is the best of the unfortunate options.  If a job needs to be re-executed, it can't only be done by 1 person in an organization, any administrator should be able to re-execute from the management console just like QlikView and QlikSense, reloading data is core to the BI platform.  Oh well.