"Keep BM Session Alive" not working in latest BM release

[darrenkhouston]

The "Keep BM Session Alive" feature doesn't seem to be working in the latest release of SFCC version 22.5.

Makes me log back in every 15 minutes, tested in Firefox and in Edge.

[amezick]

I can confirm this is happening in 22.6.

[onurorhon]

This is still broken, at least in Firefox for me.

[danieldudin]

Hello! The issue is kind of related to the background process (memory saving) suspension mechanisms in the browsers, if the tab is suspended/becomes inactive then no JS is executed in the page, hence the AJAX call that is supposed to renew the session is not executing anymore. This causes the session to expire and the said issue is completely expected.
In addition, we have not made any changes to the implementation in the past versions.

[cwang-loreal]

is there any trick or browser settings to enforce js running on special tab? Outlook for Android<https://aka.ms/ghei36> C1 - Internal use

…

________________________________ From: Daniel Dudin ***@***.***> Sent: Wednesday, February 14, 2024 9:14:52 PM To: ForkPoint/dwithease ***@***.***> Cc: WANG Clyde ***@***.***>; Comment ***@***.***> Subject: Re: [ForkPoint/dwithease] "Keep BM Session Alive" not working in latest BM release (Issue #11) EXTERNAL EMAIL: BE VIGILANT Hello! The issue is kind of related to the background process (memory saving) suspension mechanisms in the browsers, if the tab is suspended/becomes inactive then no JS is executed in the page, hence the AJAX call that is supposed to renew the session is not executing anymore. This causes the session to expire and the said issue is completely expected. In addition, we have not made any changes to the implementation in the past versions. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/ForkPoint/dwithease/issues/11*issuecomment-1943746240__;Iw!!IY5JXqZAIQ!6kSVkKN9lo8xnaT85fmEQmt_-6FpG6V0QW1Y96gd025omKEu6MYsIwHUVuUjZ4ctN4kzf647gAw5naMYywEAhDzEsA$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AS7NZ5YZ4UDB7XLPXCHCFIDYTS2EZAVCNFSM5YASGQ52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUGM3TINRSGQYA__;!!IY5JXqZAIQ!6kSVkKN9lo8xnaT85fmEQmt_-6FpG6V0QW1Y96gd025omKEu6MYsIwHUVuUjZ4ctN4kzf647gAw5naMYywGYHL_wfw$>. You are receiving this because you commented.Message ID: ***@***.***> This message and any attachments are confidential and intended solely for the addressees. If you receive this message in error, please delete it and immediately notify the sender. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized use, copying or dissemination is prohibited. E-mails are susceptible to alteration. Neither LOREAL nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

[danieldudin]

Hello, @cwang-loreal You can try the following settings:

Chrome:

Navigate to chrome://settings/performance
Go to setting: Always keep these sites active
Click "Add", to add the SFCC domains which you want to keep active

Firefox:

Navigate to: about:config
Search for: browser.tabs.unloadOnLowMemory
Set the value of the setting to: false

Please keep in mind that this is not recommended and it might worsen your performance while in other pages.

Hope that helps!
Cheers!

[danieldudin]

Re-opening since we found an actual issue with the keep session alive logic on the Firefox browser, we will soon provide an update and most likely an upcoming hotfix will be in the way at some point. Thanks a lot for your reports!!