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 

[steeefan]

You need to replace the value "CONTENTHASHHERE" in the configuration string with the actual value of your specific content hash, starting with 9fdb92:

{"contentHash":"CONTENTHASHHERE","originalClassName":"FeatureToggle","flag":"QmcTaskTableCacheDisabled","enabled":true}

[krmvacar]

Hi @steeefan ,

I did what you said and then restarted the services, but it didn't work.

[steeefan]

Can't say for sure and can't replicate, I'm not yet on May 2024.

[seblabalyerr]

Hi ,

We are still experiencing this issue in Qlik Sense May 24, despite following the suggested solution. Does anyone have a different comment?

[krmvacar]

Hi,

I upgraded to the May 2024 version and encountered this problem, please help.

I did what you said but I couldn't find a solution.

Best Regards

[Sonja_Bauernfeind]

Hello @krmvacar and @seblabalyerr 

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

All the best,
Sonja

[dwrobel]

Was able to use this to resolve our issue that just started on the May 2024 version.  Believe this may be due to a new Microsoft Security release.

[Aycan_CAG]

Hi @Sonja_Bauernfeind 

I have question about "Counters: Queries for showing numbers in the QMC can be removed to improve performance." on https://help.qlik.com/en-US/sense-admin/May2024/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

Could you please give us some details about this, which queries and numbers are mentioned?

Thanks in advance.

[Sonja_Bauernfeind]

Hello,

Please post this query in the Qlik Sense Deployment and Management forum. When you do, include as much detail as possible to what you are looking to achieve. Feel free to tag me there and I'll see if I can reach out to our subject matter experts.

You are of course also welcome to leave feedback directly on the page which you have linked.

All the best,
Sonja 

[DeepakVadithala]

@Sonja_Bauernfeind  

We are running into this issue in May 2024. Despite applying the fix ("QmcTaskTableCacheDisabled","enabled":true), there is no reprieve! We raised a case and we get link to this article.

We are not alone in this. I reached out to Qlik platform engineers/admins at two different companies and they face the same issue in Feb 2024 version, also despite applying the fix. They also have support cases raised and they all get asked to refer to this article, which isn't fixing the issue in current versions (I guess 2024 versions). 

We appreciate any help that can be offered in the matter. 

Thanks