Tasks in the Qlik Sense Management Console don't update to show the correct status after an upgrade

[Sonja_Bauernfeind]

Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.

The behaviour began after an upgrade of Qlik Sense Enterprise on Windows. 

Fix version:

This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.

Solution for August 2023 and above:

Enable QmcTaskTableCacheDisabled.

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify or add the QmcTaskTableCacheDisabled flag for these values to true
   
   {"contentHash":"CONTENTHASHHERE","originalClassName":"FeatureToggle","flag":"QmcTaskTableCacheDisabled","enabled":true}
   
   Where CONTENTHASHHERE matches the number in all other features listed in the capabilities.json.
   
   Example:
   
   
   
   This will disable the caching on the tasks table only, leaving the overall QMC Cache intact to gain performance. If you had previously set QmcCacheEnabled, QmcDirtyChecking, QmcExtendedCaching to false, please set it to true again.
   
   
4. Restart the Qlik Sense services

Workaround for earlier versions:

Upgrade to the latest Service Release and disable the caching functionality: 

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify the flag for these values to false
   • QmcCacheEnabled
   • QmcDirtyChecking
   • QmcExtendedCaching
4. Restart the Qlik Sense services
   
   

NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.

Should the issue persist after applying the workaround/fix, contact Qlik Support.

Internal Investigation ID(s): 

QB-2096
QB-5168
QB-7655
QB-17238

Environment

Qlik Sense Enterprise on Windows 

[Or]

@Sonja_Bauernfeind 

We have encountered this issue after upgrading from June 2020 to May 2021. Is it possible that the issue was not actually resolved, or that it was reintroduced after the original resolution?

[Sonja_Bauernfeind]

Hello @Or 

This could have different root causes not related to this defect. I'd recommend investigating this either with our larger community (in this forum) or contacting Support to figure it out!

[Or]

@Sonja_Bauernfeind  Thanks for your response. I reported this as a bug to the local Qlik Partner and they believe it's a known bug with the current version as well and should hopefully get corrected soon.

[Serkan]

@Sonja_Bauernfeind  I can also report that we discovered this bug also with the latest QS-Version (May 2021) and would appreciate if you can communicate it to R&D.

[Sonja_Bauernfeind]

Hello @Serkan 

I spoke to a subject matter expert around this and a support case is required to proceed, as the defect itself is meant to be resolved and needs to be re-investigated. I am not certain if @Or has an ongoing ticket with Qlik Support, so it may be necessary for someone else who experiences the issue to log a ticket with us so that the investigation can be correctly started. 

All the best,

-Sonja

[shanemichelon]

I just upgraded a client site to Aug 2021 SR2, and the issue is still present.

[BuTbka]

There is also the same problem. Only root users can see the correct status in the QMC. Others only see the correct status when any filter is applied. Refresh button in QMC or browser does not help. Aug 2021 SR3 disabling caching did not help.

[Jure]

I have upgraded to August 2021 SR3.  This issue was still present. Also I am root admin.

Now I made changes suggested in this topic. The issue is gone.

Of course also this orange highlighting of reload button in QMC to notify you that status of some task has changed doesn't work anymore.

[Jure]

Also I have restarted all services after the change in capabilities.json

[BuTbka]

@Jure what about other users without root admin role?