Forum Discussion

ChrisWalsh's avatar
ChrisWalsh
Community Member
10 years ago

FORCED_COMMIT_TIME value of 60000 (60k)

When publishing a Storyline 2 course for LMS, the configuration.js file has a setting " FORCED_COMMIT_TIME " which is set to "60000".   Am I safe to assume that this is the number of millisecon...
storyline 360
KatieRiggio's avatar
KatieRiggio
Staff
6 years ago

Tuesday morning news, all! 🗞

A hotfix for Storyline 360 is ready: We fixed the issue where the FORCED_COMMIT_TIME variable in the scormdriver.js file defaulted to a value of 0 in the previous update, preventing courses from sending 'keep alive' messages to an LMS to keep learners' sessions from timing out. This update restores the default value of 60000, which sends a 'keep alive' message to the LMS every 60 seconds.

Thank you for bringing this up, and let us know if you have any questions! 

MikeZaluski's avatar
MikeZaluski
Community Member
6 years ago
Katie Riggio

Tuesday morning news, all! 🗞

A hotfix for Storyline 360 is ready: We fixed the issue where the FORCED_COMMIT_TIME variable in the scormdriver.js file defaulted to a value of 0 in the previous update, preventing courses from sending 'keep alive' messages to an LMS to keep learners' sessions from timing out. This update restores the default value of 60000, which sends a 'keep alive' message to the LMS every 60 seconds.

Thank you for bringing this up, and let us know if you have any questions! 

Hi there

Are there any plans to add such a fix/functionality for Rise?

Or is there a reason that the scorm commit and keep-alive messages are different between StoryLine and Rise?

The below was posted in this thread a year ago "Our team found that Rise 360 courses are not sending keep-alive messages to the LMS, even if the FORCED_COMMIT_TIME variable is changed the value from 0 to 60000." is this seen as a bug?