How often does Rise ping the LMS?

So happy to read that this will be fixed! 

Hi there

 Thanks to the contributors to this thread – it’s been helpful to understand the issue one of my clients is having.

 As well as increasing the timeout time of the LMS we’ve added the ‘exit course’ button* in Rise & encouraged people to ‘save their progress’ by using this button. This has meant more people are regularly saving where they've got to on the LMS with fewer people leaving their courses idle while going to meetings or having lunch etc.

 HTH

 Justin

* You add this button, which stays at the top right of the screen in Rise, by selecting the option when exporting as a SCORM file.

This is also a major issue for me. It effectively makes xapi uses of rise inviable in most use cases. A person could spend a whole hour on a course accidentally close the tab and be quite upset.

The behavior described in the first response of this thread is exactly what we want. Its quite concerning that an issue like this has taken more than a week to be fixed in my opinion.

I just published a course today  from Rise 360 and this is the value for the force commit variable that appeared by default. Has the update to set the default value to 60 seconds been rolled back for some reason?

var FORCED_COMMIT_TIME = "0";

Hi Sharon!

When you extract the Rise 360 SCORM output file, what do you see for FORCED_COMMIT_TIME when you open the driverOptions.js file in the scormdriver folder?

You should see scope.FORCED_COMMIT_TIME = 60000; (60000 milliseconds = 60 seconds)