Stream are not visible or available on the hub in Qlik Sense May 2022

[Benoit_C]

After upgrading or installing Qlik Sense Enterprise on Windows May 2022, users may not see all of their streams.

The streams appear only after an interaction or a click anywhere on the Hub.

This is caused by defect QB-10693, resolved in May 2022 Patch 4.

Environment

Qlik Sense Enterprise on Windows May 2022 

Workaround

To work around the issue without a patch:

1. Locate and open the file: C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   
   
2. Modify the following line:  
   
   {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"HUB_HIDE_EMPTY_STREAMS","enabled":true}
   
   Set it from true to false: 
   
   {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"HUB_HIDE_EMPTY_STREAMS","enabled":false}
   
   
3. Save the file.
   
   If you have a multi node, these changes need to be applied on all nodes. 
   
   Note 2: As these are changes to a configuration file, they will be reverted to default when upgrading. The changes will need to be redone after patching or upgrading Qlik Sense.
   
   
4. Restart the Qlik Sense Dispatcher service AND the Qlik Sense Proxy Service 
   
   Note: If you have a multi node, all nodes need to be restarted. 

Fix

A fix is available in May 2022, patch 4.

Streams will show up (after a few seconds) without the need to click or interact with the hub.

Important NOTE about feature HUB_HIDE_EMPTY_STREAMS:

When you activate HUB_HIDE_EMPTY_STREAMS, you will have an expected delay before all streams appear.

To improve this delay, from Patch 4, you can add HUB_OPTIMIZED_SEARCH (needs to be added manually as a new flag). As of now, HUB_OPTIMIZED_SEARCH tag will be available in the upcoming August 2022 release and is not planned for any patches (yet)

If this delay (seconds) is not acceptable, you will need to disable this HUB_HIDE_EMPTY_STREAMS capability.

Cause 

This defect was introduced by a new capability service. 

Internal Investigation ID(s) 

QB-10693

[korsikov]

What best practice for speedup /myspace request for large qs clusters? 

Disable HUB_HIDE_EMPTY_STREAMS  it not a option