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 milliseconds between regular LMSCommit() events that Storyline 2 triggers (unless explicit ones are issued such as after an assessment)?This value equates to 1 minute however I seem to see LMSCommit() events running every 10 minutes. Is there a miscalculation on the number conversion here? Am I missing something else? Also, having searched the course for the value "FORCED_COMMIT_TIME" (all files), there is only that one occurrence of the value. Is the value actually being used? Thanks, Chris

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!

Hi Chris, I double checked with our team, that the 60000 = 10 mins in Articulate for the LMS Commit time, and you'll see another thread with that time mentioned here. If you'd like to see the data we're passing to your LMS, I'd recommend enabling LMS debug mode as detailed here. If you're still having difficulty with it and would like to investigate further with our Support Engineers we're happy to do so and you can reach out to them here.

Hi Ashley, Thanks. That has explained a lot of what is going on (despite being related to Studio '09). I've checked the lms.js file that SL2 packages up with the course and found: setInterval("ForceCommit()", 600000); So, SL2 uses a 600000ms (10 minute) interval rather than a 60000ms (1 minute interval) SL2 is NOT using the value in configuration.js despite it making sense to do so. The value is hardcoded in the code rather than in configuration.js. There is no option (such as setting the value to 0 like the comment suggests in configuration.js) to switch off auto-committing. One would have to comment out the line of code in lms.js. I can propose a change request for the developers to: Amend configuration.js to set the value of FORCED_COMMIT_TIME to 600000 (10 minutes) in line with a 10 minute interval currently hard coded in lms.js. Amend lms.js to make use of the FORCED_COMMIT_TIME rather than hard coding the value. This will make it a lot easier (and a lot less misleading) to course builders who wish to customise the forced commit time. Thanks, Chris

Hi Alyssa, thanks for writing back. Sorry for being vague in my former post. Yes, I'm seeing a problem with Rise that's very similar to this conversation about Storyline. For the purpose of establishing some context, here's how Storyline works: Storyline calls the ForceCommit() function at an interval that's defined by the FORCED_COMMIT_TIME variable in configuration.js. With Storyline, even if the communication to the LMS is severed after some time has passed, I can still see from the LMS communication log that data was written back to the LMS up to the point where the communication was severed. It took place every 60 seconds, as defined by the FORCED_COMMIT_TIME variable. This is great! This is as it should be. Rise does not have the same behavior. Even though the scormdriver.js file declares the FORCED_COMMIT_TIME variable, it is not being utilized even if it's set to 60000 (the same default value of the Storyline variable). This behavior in Rise is the same as the original post by by Chris Walsh. (But, of course, the original post was for Storyline - which now works as expected.)

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

FORCED_COMMIT_TIME value of 60000 (60k)

38 Replies

MikeZaluski
Community Member
6 years ago
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
- LaurenDuvall
  Staff
  6 years ago
  Hi Mike!
  
  Thank you for adding these details! I see that you were working with my teammate, Phil. Our Support Engineers are available in a support case if you need additional help!
AlyssaGomez
Staff
5 years ago
Hi everyone! Our team has made improvements to the FORCED_COMMIT_TIME variable in Rise 360. Newly exported Rise 360 courses exported using SCORM 1.2, SCORM 2004, or AICC will communicate with the LMS every 60 seconds, as well as when you navigate to each new lesson. This change doesn't apply to courses exported with xAPI or cmi5.

Please let me know if you have any questions about this enhancement!

Forum Discussion

FORCED_COMMIT_TIME value of 60000 (60k)

38 Replies

Related Content

Tips & Tricks: How to Get the Most Value Out of AI Assistant

SL360 default values on dials

Layers not displaying correctly based on variable value

Submit Button Interaction Values

Values in variables not changing correctly

Learn

Connect

Discover

Community

Company

Trust Center