function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Jugbeer BholaJugbeer Bhola 

Enable secure and persistent browser caching to improve performance label issue

Could someone please call out the negative impact of not using the setting of:

Enable secure and persistent browser caching to improve performance

I know the setting helps components load faster but what negative impact will it have in other respects?

Intermittent failure of labels loading have been reported an environment.  

This occurs when a component references a label: import randomlabel from '@salesforce/label/c.randomlabel';

The only solution offered  is here:

https://trailblazer.salesforce.com/issues_view?id=a1p4V00000042DYQAY&title=custom-labels-imported-in-lwc-are-not-rendered-intermittently-in-communities

This recommendation suggests unchecking the box in Session Settings of:

Enable secure and persistent browser caching to improve performance

If I uncheck the box am I going to have an array of issues.  If I do not then the users labels do not load from time to time. 

VinayVinay (Salesforce Developers) 
Hi Jugbeer,

The caching setting improves page reload performance by avoiding extra round trips to the server. Disabling secure and persistent browser caching has a significant negative performance impact on Lightning Experience and make sure you enable this setting in production orgs once you have good testing in lower orgs.

Check below reference.
https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/perf_secure_browser_caching.htm#:~:text=Enable%20secure%20data%20caching%20in,Only%20disable%20in%20these%20scenarios.

Also this bug would be fixed ASAP in coming days and you can try using second workaround mentioned.

2) Use @wire apex call: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.apex.



Please mark as Best Answer if above information was helpful.

Thanks,
Jugbeer BholaJugbeer Bhola

Thank you for the reply.   This is very disappointing that there is such an internal failure. Hope you are correct and this this bug will be fixed ASAP in coming days.

I cannot apply the second work around.  There are well over 300 LWC components that would have to be rewritten and regression tested.  

I will wait to see if this gets resolved soon.   If not I will have no other choice than to uncheck the box until it is fixed.  

Thanks
Jugbeer BholaJugbeer Bhola
Salesforce has notified me that they will fix this in Summer '23.  Until then we are forced to tell the user to refresh thier page.