How to fix time out issues where tracking won't allow user to complete?

[Learning_Discovery]

SAP Success Factors LMS. (latest version)
SCORM 1.2 uploaded/generated from Articulate 365. (latest version)

Training packages works for multiple users/across multiple accounts. However, some users experience inability to complete training(s) after timing out their session. (Can find no issues in the trainings themselves, tested across multiple browsers and multiple systems with no issues. This seems to be a random issue and does not seem to be narrowed in on one user or even one training.  The only common point seems to be that they either multi-task away from the LMS session browser window or let their training sit open overnight so it times out...consequently they are able to finish the training in the buffered window/session - but it doesn't track properly and won't officially complete for them in the LMS backend. 

Wondering if there is a way to mitigate/avoid this? Perhaps an auto log-out feature/setting? (does one even exist?)

[ChrisMayAtDelta]

You might want to check out the users' browser setting. Third-Party cookies (AKA cross-site tracking) must be enabled or users will time out after 30 minutes.

[Learning_Discovery]

Thanks - that's a good tip, I'll check out out.

[PL1]

@Learning_Discovery, here you can find additional details to be verified: Common Problems and Solutions for SCORM 1.2 and AICC Content. Furthermore, if the user's computer enters sleep/suspend mode, the internet connection will potentially terminate, leading to the lack of ping that keeps the session active, causing the logout.

[Learning_Discovery]

Hey thanks for that - I'll check out that document. But if there is a lack of ping (if the computer goes to sleep/suspend) and the session remains "open" is there a way around it? Like an automatic logout of the seesion, rather than letting the user carry on as if nothing happened? (I suspect this happens since user's computer likely buffers the remaining course content...)

[PL1]

The system has a 30min. hard coded timeout. The details of the KBA 2088893 can be reviewed. After the 30min. with no ping or no internet, if for some reason the user doesn't see the logout/timeout on screen, the browser logs should confirm it.