topic Re: Managing Large Apps in Management & Governance

Managing Large Apps

Adfc_NZ — Mon, 16 Feb 2026 01:31:01 GMT

Hi,

We have some spaces with the "Large Apps" capability activated, and we are looking for a way to see a history of when the large apps capacity/limit was reached (which then causes the users to not be able to open the app until we go below that threshold).

I know that in the Admin Center Home there is a horizontal barchart displaying the current limit (what we purchased) and the utilisation.

But this only gives us a "that day" kind of analysis, and we are trying to identify patterns and trends that may indicate or even allow us to predict when we are going to go over the Large Apps threshold again.

Is anyone aware if this already exists in a Monitoring app (can't see it, but doesn't hurt to ask 🙂 ) and if it doesn't any way to build that information?

Thank you.

Re: Managing Large Apps

Dave_Channon — Mon, 16 Feb 2026 14:35:20 GMT

@Adfc_NZ take a look at https://github.com/qlik-oss/qlik-cloud-app-analyzer - the app analyzer has large app capacity utilisation over the day in one of the charts on the first sheet.

Re: Managing Large Apps

Adfc_NZ — Mon, 16 Feb 2026 22:16:16 GMT

Thank you Dave, and that should teach me/us to update our Monitoring apps more regularly as the version we currently have does not have that level of detail.

However, after I uploaded the new version, I keep getting a "out of memory" error when reloading. I reduced a couple of variables to the value '60' and that allowed the app to reload, but weirdly the details in the app show only 2 days of data. Any inputs on what might be happening?

Re: Managing Large Apps

PrashantSangle — Tue, 17 Feb 2026 02:44:31 GMT

if you have capacity based license then goto

administration > Setting > tenant tab > Detail Consumption report section > Distribute >

You will get one report in your Personal space.

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/usage-metrics-app.htm

Regards,

Prashant Sangle

Re: Managing Large Apps

Dave_Channon — Tue, 17 Feb 2026 09:40:07 GMT

Do you have a lot of apps in the tenant?

Possibly it's because on that first load it managed to create some QVDs, and it's basing the incremental load off of those files. If that's the case, delete any existing QVDs created from the failed run and retry, let me know how you go.

Re: Managing Large Apps

Dave_Channon — Tue, 17 Feb 2026 09:40:51 GMT

@PrashantSangle the detailed consumption report does not include large app consumption data. It is not suitable for this purpose, unfortunately.

Re: Managing Large Apps

Dave_Channon — Tue, 17 Feb 2026 09:41:33 GMT

For others finding this topic later, please consider reviewing https://community.qlik.com/t5/Official-Support-Articles/How-to-take-control-of-your-Qlik-Cloud-subscription-a-guide-to/ta-p/2542870 to learn about all the monitoring options available in the tenant.

Re: Managing Large Apps

Adfc_NZ — Tue, 17 Feb 2026 20:26:56 GMT

Hi Dave,

First of all thank you for your reply. 🙂

Answering your questions, yes we have close to 2k apps between DEV, QA (Shared) and PROD (managed) spaces and the first reload attempt didn't create any QVDs.

I just tried reloading it again and after 17 minutes it errored out with the "The memory limit for the request was reached".

Should I raise a support ticket? The existing "old version" of the App Analyzer reloads successfully every day in under 2 minutes. I understand the new version has way more information in it but one would expect it to reload, and I am sure we are not the biggest Qlik client app-number-wise.

Thanks.

Re: Managing Large Apps

Dave_Channon — Wed, 18 Feb 2026 13:54:41 GMT

Which version did you come from? I'm surprised at such a difference, unless you were on an older version.

One easy option would be to assign large app capacity to the monitoring app space and reload it until success there, or you could try to leverage the batch mode as documented here: https://github.com/qlik-oss/qlik-cloud-app-analyzer/releases#:~:text=Added%20the%20ability%20to%20batch%20reload%20app%20metadata.%20This%20was%20implemented%20due%20to%20reloads%20timing%20out%20with%20tenants%20that%20contained%20more%20than%2010k%20apps.%20If%20the%20tenant%20contains%20more%20than%2010k%20apps%2C%20this%20option%20will%20be%20mandatory.%20The%20batch%20reload%20process%20is%20as%20follows%3A

Is it possible that your subscription has less than 5GB standard tier limit?