FORCED_COMMIT_TIME value of 60000 (60k)

Hi Alyssa, thanks for responding, sorry I forget to check back on this thread.

Yes we have some long lessons, and seem to have a bit of a history of users losing progress across many of our Rise courses, usually when they try to complete over a number of sittings. This has become more prevalent recently as we have released a longer video based course, that if users do the right thing and watch everything, need to do over a number of sittings.

The course works fine for me and "most" users on Chrome and Firefox, progress is saved automatically as expected. On IE11 tho (which sadly is still my departments default browser) progress is only saved by the use of the "exit course" button in Rise or the "save and close" button in our LMS, i have been able to reproduce this error. This has occurred for courses published as SCORM 1.2 and also SCORM 2004 v3 - which we advised to use for Rise courses due to SCORM 1.2's lower data-suspend value.

I raised a case and provided the course to Articulate, and received the response that as it works on SCORM cloud then the course is fine. I would assume our LMS (Learning Suite, from IMC multimedia) isnt as forgiving as SCORM cloud (which seems fairly common across the threads i read here) and I have also raised a ticket with IMC for assistance. Initially they advised the below, which is why i have been trying to read up on scorm_commit.

"We suggest that Scorm WBT takes care, that at least the critical data, such as score raw, lesson status, completion status and success status are set in the session, immediatelly after they have changed. The data should also be commited at that point (SCORM commit). I´m not sure, at what point of the session or how often your content currently transmits the scorm data. This is completely up to the content tool. It should be commited at least periodically, and NOT only at the end/closing of the session."

FWIW i feel the issue is somewhere between our LMS, our default browser being IE11, and a little bit Rise as we not see these issues with StoryLine.

Cheers

Mike Z