Qlik Sense Patch Causes Data Connections to load very slowly in Load Editor

[craigbence]

We recently updated our Qlik Sense version to Qlik_Sense_update_Feb2024_Patch4. Now, each time we access the Load Editor in an application in our Personal Work Stream, takes roughly 2-3 minutes to load the Data Connections. Prior to the patch, these Data Connections would display within seconds. While the Data Connections are loading, the editor is basically at a standstill. 

Has anyone experienced this behavior? Any recommendations on how to correct this situation would be appreciated!!

[SivenM2020]

Thanks, please let us know the outcome of your case, and if a new SR is going to be released

[SivenM2020]

Thanks, our customer just tested - removing the SAP connector resolved the issue, but we are not sure if anyone uses it.

So hopefully Qlik provides a permanent solution.

[Hoover]

@henrikalmen , tested your solution, it works! Will have to use this workaround until its fixed in the next Patch.

[shaun_lombard]

Just remember to put the folder back before applying future patches because it fails if the folder is not there (presumably only for patches that update those files), which is what happened to me.

[Tool_Tip]

Dear Henrik Almen,

We have removed the SAP connector, and it appears that the issue has been resolved. However, I do not consider this a permanent solution, as multiple clients are likely to use SAP. Simply removing it from the platform is not a sustainable fix.

We will need to wait until Qlik confirms and officially accepts this resolution. Until then, this should be treated as a temporary workaround.

Thank you.

[henrikalmen]

Absolutely, it must be temporary. Not to mention those who actually need that connector. 

See also Important remark from @shaun_lombard

[Sonja_Bauernfeind]

Hello everyone,

A defect ID is available for this issue. See Qlik Sense Enterprise on Windows May 2025: Slow Data Load Editor.

All the best,
Sonja 

[Tool_Tip]

Dear Sonja
When we can expect next patch or version ? 

[janyf]

Patch 6 , which was released yesterday, fix this issue on my test environment. 
Although there is no direct mention of SUPPORT-6006 in release notes. 

[henrikalmen]

I just got an update on my support case regarding this, and they're not finished: "Your reported issue related to this case it is still under investigation by our R&D team and we appreciate your patience." But if patch 6 solved the issue anyways, that's good of course. 🙂 I haven't patched yet. Anyone else tried patch 6 and noticed any difference?