Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello everyone,
I have a regular application with several charts and filter panes, and I have an issue I couldn't find anywhere else on this forum.
When I'm using filters, I expect all my charts to dynamically update, but it seems like some won't work as intended and just stay "frozen".
For example, let's say I have 7 charts on my sheet. When filtering on a country, 5 charts will properly update to fit the selected country, while 2 others will just stay in their initial state.
Directly clicking on these charts to filter them (on whichever dimension they are based on) seems to "unfreeze" them, as they will work properly and won't freeze anymore.
The charts affected are not always the same, and sometimes everything will work properly. This issue seems to appear completely randomly (but often enough to be troublesome), so I don't think it comes from my data model or my graphs, but from Qlik Sense itself.
I'm using QlikSense Enterprise, version August 2023 patch 8.
If you have any idea at all on how to fix it, I would be really grateful.
C. Delecourt
Hi,
That's quite strange ! No Set Analysis nor Alternative State ?
Can you share Qlik Sense complete logs using the Qlik Sense Log collector, on a timestamp when this behavior appears ?
Regards,
Hello Maxime, some charts use Set Analysis, some don't, and both types can be affected by this problem. I don't use Alternate States in this application.
I don't really know how the Log collector works, and I don't have the rights to access it anyway (I'm just a ContentAdmin). What information are you looking for exactly, and how could I help you get it ?
Ok let start to check some browers or users issues:
Then, you should ask to your deployment admin to look for "Error" or "Warning" in the engine or the repository logs. Maybe enable the debug look too ?
This application was tested by 4 users (including myself), and each one of us encountered this issue several times. Regarding browsers, I think everyone uses Edge, but I'll try to test it on another browser.
Also thanks for your advice, I'll tell the people in charge of the deployment to look for these keywords.
I'll come back here as soon as I have their answer, in the meantime thanks for your help and your time.
#1, If the user refresh the page and is this still same?
#2, What if the user clear the cache and tried few more times, is this still same?
#3, My best guess is that the 2 charts are complex and huge data points, did you try to filter more to see the changes?
#4, Did you used any Analyzer tools (Ex,. QSDA pro to see the performance)?
#5, If you have access to telemetry dashboard, there you can see some more about the charts that you see the slowness.
Hello Anil, thank for your help, I'll try to answer each point :
#1 It depends, sometimes reloading unfreezes the charts, sometimes it doesn't. The issue is really random
#2 I tried to clear the cache but the issue still remain, my charts still randomly freeze
#3 It doesn't matter how many filters I put when a chart is frozen, it stays the same and can only be unfrozen when i directly interact with it. Also, it doesn't always happen on the same charts, it mostly happens on a stacked bar chart (which uses 2 dimensions), but can also happen on a simple bar chart.
#4 I don't really know or use any Analyzer tool, I'm only a Content Admin and don't have much freedom on the infrastructure, only on my App, its Data and its Stream
#5 I have access to the 2 default monitoring apps (License Monitor and Operations Monitor), but I don't think the others are installed. Is it what you're talking about ?
I just noticed something which could help understand the cause of this problem
It seems like the "chart freezing" only occurs on the published version of the app, it doesn't happen on a duplicated version (be it a duplicated application in my workspace or a duplicated sheet on the stream)
Very strange behavior...
Have you tried to Publish and replace the app with a duplicated one ?
Yes I did, I published several versions of the app since I discovered this problem, and it's still the same.
I also have another version of the app with different data (same format, but different environment). This behaviour happens on both versions of the app.
I guess it's because they both come from the same original app, but it could also be a bug triggered by the charts I chose, the "shared" aspect of the app, or something else...