Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
AM4
Contributor
Contributor

Refresh Application Through API

Hi Qlik,

On of the requirements in a POC I am currently working on is we need it to refresh at least every 5 to 30 seconds. We

 investigated the  automated workflows (automations) but due to costs we had to find a work around. We then created a rest API in a C# application that checks if there is any refreshes that is currently running. If not refresh the application and return the refresh ID. We are able to see whether the refresh is still in progress and based on when it is done trigger a new one. This works well except that  sometimes when we run the API the refresh gets put in a Queue that sometimes takes up to 10 minutes to trigger the app refresh. The refresh itself of the application takes 11 seconds. When we run the REST API directly in a Qlik extension it does not get added to a queue.

Could someone please explain why this is or how  we can avoid our refreshes be put in a queue?

Also please explain why we have queues if there is no other applications running?

 

Please let me know

Kind Regards

 

Labels (2)
1 Solution

Accepted Solutions
SteveAO
Employee
Employee

Hello AM4 from CIM Solutions,

 

I hope all is well.

All requests are handled from a queue. The priority and wait ultimately depend on our documented limits (https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_QlikAutomation/introduction/...) and rate-limited allocation to capacity based on your license. 

 

However, as an alternative, you can extend your current C# service to call the reloads directly with the app Id(s) by dint of a DoRelaodEx with a WebSocket client to the Qix Engine: https://qlik.dev/apis/json-rpc/qix/doc#%23%2Fentries%2FDoc%2Fentries%2FDoReloadEx

 

Also, please take a look at our examples for managing incremental reloads so that the apps that you process selectively obtain deltas from your data source: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/LoadData/use-QVD-files-i...

 

 

Otherwise, please take a look at the pipeline features in SaaS to extend further what you might intend to do in landing the data in your SaaS tenant and enable the business users consuming your landed data: https://www.qlik.com/us/products/cloud-data-integration

View solution in original post

1 Reply
SteveAO
Employee
Employee

Hello AM4 from CIM Solutions,

 

I hope all is well.

All requests are handled from a queue. The priority and wait ultimately depend on our documented limits (https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_QlikAutomation/introduction/...) and rate-limited allocation to capacity based on your license. 

 

However, as an alternative, you can extend your current C# service to call the reloads directly with the app Id(s) by dint of a DoRelaodEx with a WebSocket client to the Qix Engine: https://qlik.dev/apis/json-rpc/qix/doc#%23%2Fentries%2FDoc%2Fentries%2FDoReloadEx

 

Also, please take a look at our examples for managing incremental reloads so that the apps that you process selectively obtain deltas from your data source: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/LoadData/use-QVD-files-i...

 

 

Otherwise, please take a look at the pipeline features in SaaS to extend further what you might intend to do in landing the data in your SaaS tenant and enable the business users consuming your landed data: https://www.qlik.com/us/products/cloud-data-integration