FORCED_COMMIT_TIME value of 60000 (60k)

Hi Ian! Your Rise 360 course will communicate to the LMS when you navigate to each lesson.  There isn't a way to otherwise force a commit to the LMS. Can you tell us more about the issue this is causing for you? Are your learners timing out and losing their progress while taking your courses? 

Thanks Alyssa. We are embedding the majority of the learning experience within an iframe within Rise, so there isn't much navigation happening from lesson to lesson. As a result, exactly as you said, some learners are timing out and losing their progress, therefore we were hoping to use the FORCED_COMMIT_TIME variable to periodically force LMS Commits to happen in the background. 

I understand, thanks Ian. For now, there isn't a way to use the FORCED_COMMIT_TIME variable to periodically force LMS Commits to happen in the background. We'll let you know if that changes in the future!

Hello,
I'm the original poster of this discussion thread.  Obviously things have moved on quite a bit from when I posted it four years ago.

However, we've started noticing that Storyline 360 (latest versions) are no longer setting FORCED_COMMIT_TIME to 60000 by default but to 0 (which means no auto-commit).  Furthermore, the location of this configuration option has moved from "configuration.js" to "lms/scormdriver.js".

Is there any announcement on these changes that I can read up on?  I'm particularly interested in knowing why an auto-commit has been switched off by default (as we're going to need to manually set this back to 60000 after each publish).

Note: We're publishing to SCORM 1.2 and SCORM 2004 and to "html5 only".

Thanks, Chris

Hi Chris!

Thanks for updating us! I'd like for our Support Engineers to work with you so that we can investigate further. I've just opened a case on your behalf and sent over a brief email. You'll hear from our team shortly!

I'm with you Chris! The switch from SCORMFunctions.js to scormdriver.js is really throwing us for a loop. The new scormdriver.js is the same code base that is used for Articulate Rise. When I expressed dismay over the lack of functionality for the FORCED_COMMIT_TIME variable in the Rise code base, it sounded to me like there was no remediation planned. But hopefully if it gets fixed for Storyline, the fix can be translated to Rise as well.

This is a major issue for our company with over 200,000 employees who are now faced with a greater likelihood that their progress through a course may be lost if there is a network error. And we have over 200 Storyline developers who are producing projects .

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.

• Check out the release notes for more details
• Follow these steps to see all the latest fixes

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

Thanks Kate.  That's great news.

Please note however that 60000 equates to 1 minute not 10 minutes (as value is in milliseconds, not centiseconds).  (This info is also incorrect in their change log)

You're right and good catch, Chris!

Our team corrected the version history, and I'll update my previous post to reflect that. Thank you!

Hi Mike! Thanks for checking in on this. This is not a bug, but rather just a difference in the way Storyline 360 and Rise 360 communicate with your LMS. Rise 360 sends a keep-alive message to your LMS when you navigate to each lesson.

Does your course have long-running lessons that are causing learners to time out? If so, would you mind if we had a look at your course? If that works for you, you can send the LMS output file to us privately here.