Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

More frequent scheduled App reloads on Qlik Sense SaaS: more than once per hour

Ron_van_Rooij
Contributor II
Contributor II

More frequent scheduled App reloads on Qlik Sense SaaS: more than once per hour

Attachments

Challenge in Qlik Sense SaaS
In Qlik Sense SaaS, we can only select 'hourly' as smallest refresh schedule for an App. Not every 30 minutes. Not every 10 minutes. See attached screenshot.

Description of idea
To have the possibility to set the reload schedule for an app as "every X minutes". 

This functionality was available in QlikView QMC. Not anymore in Qlik Sense SaaS.

Value proposition
Some apps are looked at multiple times a day by end users, e.g. apps that display *today's* sale performance for online shops. An hourly refresh is not frequent enough to detect possible issues early, during the day. Or to do daily management activities. The users would require the sales data to flow in Qlik app every 30 minutes to have a good grip on their business. 

Additional context
If this feature would risk taking too much Cloud CPU/Memory, then the Qlik SaaS could 'assess' the resources required for the app reload first. If an app would reload very quickly, then Qlik SaaS should allow for a refresh schedule "every X minutes". If not, then the option would be greyed out and user first needs to optimize the app.

Tags (2)
26 Comments
aritting
Creator
Creator

we tried the Qlik Automation to replace the functionality of reloading more frequently than an hour or cascading parallel or serial tasks but very quickly consumed all the available minutes we had for free to use automation and if we kept it up would have received an enormous bill from Qlik.  This is not an acceptable replacement for the functionality in QlikView Publisher and Qlik Sense Enterprise

LuZhang
Contributor
Contributor

Agree!!

scottduthie
Partner Ambassador
Partner Ambassador

Agreed - I think there's a solid use case for separating simple chained reloads of Qlik apps from other workflows that consume Application Automation credits.  Especially given chaining app reloads, binary loads, layered qvd creation stages etc. are part of Qlik's native best practice workflow.

Viktors
Partner - Contributor
Partner - Contributor

Agree!!! task chaining would be natural replacement for this missing funcionality, but it easily goes above free limit of automation runs.  

Meghann_MacDonald

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.

Ideation
Explorer II
Explorer II
 
Status changed to: Closed - Archived