FORCED_COMMIT_TIME value of 60000 (60k)

Hi Chris,

Thanks for reaching out here and I found another earlier thread where he did the conversion to 10 mins vs. your 1 min. Are you having similar difficulties with data not being tracked correctly to your LMS? Have you gone through the LMS troubleshooting steps here? 

If my memory serves me well, I believe this was set high so as not to add an overhead to the LMS, I also understand you can change this to any value you are happy with.

Thanks Phil.  I know we can change the value (a simple edit to the js file) and why you may not want to set the value too high or low.  I'm just questioning whether it is actually being used by the course and if it is, whether it is treating the units as milliseconds.  

The reason I question it is because I can't see anywhere where any JavaScript actually reads this value and the rate of LMSCommit() don't seem to tally with the value set.

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,

1. SL2 uses a 600000ms (10 minute) interval rather than a 60000ms (1 minute interval)
2. SL2 is NOT using the value in configuration.js despite it making sense to do so.
3. The value is hardcoded in the code rather than in configuration.js.
4. 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:

1. 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.
2. 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 Chris,

I can certainly pass that along as a feature request - but hopefully we at least got to the bottom of the behavior you were seeing! 

Yes we did.  And thanks for adding it to the feature requests.

No problem Chris - and we don't share information in terms of product roadmaps, so I can't say when there may be such a feature in Storyline or Studio but once we have information about an update or new release, we'll be certain to let folks know. 

Hi, we're two years on and we're still seeing freshly published courses committing every 10 minutes instead of every 1 minute despite FORCED_COMMIT_TIME = "60000";. 

We've shed a bit more night on it though:

• Running a course in Google Chrome shows an auto- ommit every 1 minute
• Running a course in IE11 shows an auto- ommit every 10 minutes

We've tried two different courses and it's the same.  

So why is IE11 different to (say) Chrome?  Well IE11 is running the course in "Flash" whereas Chrome is running it in native HTML5. 

So we've disabled Flash in IE11 to run the Native HTML5 and we then got the correct 1 minute auto-commit.

So this might be a bug in the Flash framework.  Are you seeing the same situation?  Thanks.

Hi Chris,

I know this discussion has gone on for some time, but I wanted to confirm what version of Storyline you're using? We had an issue in Storyline 360 where the HTML5 LMS output sends a status to the LMS even if we set var FORCED_COMMIT_TIME = from 60000 to 0. That was fixed in Update 16, and it'll be fixed in the next update of Storyline 3 as well.

If you are still seeing something odd in your files, could you connect with our Support team so that we can take a look!