Unresponsive Behavior in App When Accessing Specific Sheet

[yh2023]

I need assistance with an issue I am experiencing in the Qlik app.

I can successfully open an app; however, when I attempt to access a particular sheet, the application becomes unresponsive. I am unable to scroll or edit the sheet after few seconds, and it appears to be stuck.

Then I get the following screen:

I would appreciate your prompt attention to this matter and any guidance or solutions you can provide to resolve the issue.

Thank you for your assistance.

[Anil_Babu_Samineni]

@yh2023 Please try to close the session and retry. It says that you don't have enough memory and CPU capable to access the portal.

[yh2023]

@Anil_Babu_Samineni thank you so much for the response. I closed the session, cleared the history, and cleaned the cache memory, but despite these actions, I am still encountering the same issue.

[Anil_Babu_Samineni]

@yh2023 Please show Task manager and Memory side by with CPU from the node where you open and also locally from your machine.

How you know from which node the app is open? You can drag KPI object and use this =ComputerName() to find out that.

[yh2023]

@Anil_Babu_Samineni I'm using Qlik Sense SaaS, I am not sure examining the Task Manager might not provide relevant insights. However, upon opening the sheet, the Task Manager shows the following data:

[Anil_Babu_Samineni]

@yh2023 If it is SaaS, the model is same but now sure how you managed the sever allocation. If this is within your organization Infra, you can check logging in to server and find out.

If it is Qlik managed, please check with them. 

But the way, Is this same for all apps?

[yh2023]

@Anil_Babu_Samineni The server is managed by Qlik, and the problem is with just one app. When I open a specific sheet in that app, everything crashes, including other apps opened in other tabs. That specific sheet has four straight tables, each with about 10 columns and uses Rank function(for all the tables).

[vincent_ardiet_]

Try to keep only one object, then 2... maybe you will be able to identify if one only is creating the issue.

[Or]

I'd suggest opening the app without data, or if that's not possible, open the app and heavily filter it (keeping only one row or something similar). If you are then able to open the sheet, then the issue is likely that one of the objects on the sheet is causing it to freeze. That would typically be a case of either an unusual expression, or more likely, some sort of Cartesian join being applied due to using fields from tables that are not connected by any keys.

[Anil_Babu_Samineni]

@yh2023 Please try to use any tools like QSDA (Qlik sense Document Analyzer) and see the performance?