FORCED_COMMIT_TIME value of 60000 (60k)

Hi Ashley,
It is still occurring in the latest version of SL360 and SL3 (as of 12/06/2018 - our authors update as soon as updates come out).

The issue related to using the default value of 60000 rather than when setting the value to 0).

I've raised it as Case No 01407604.

Thanks,

Chris

Hi, we have a SL3 course sending LMS calls every 1 minute. Are you saying the ability to edit this is not available? I'm on SL3 v3.4. I've edited the configuration.js file but as others mentioned it does nothing.

Hi Dave,

Really sorry you're running into this, as well. 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.

We'll keep you posted and let you know as soon as that fix is released!

Hey Dave. I'm excited to let you know that we just released update 5 for Storyline 3! It includes new features and fixes - check them all out here.

One of the fixes addresses an issue where HTML5 output sends a status to the LMS even if we set var FORCED_COMMIT_TIME = from 60000 to 0.

Here’s where you can download and install the latest version of Storyline 3. Let me know how you make out!

I'm wondering if the same problem exists for Rise. In scormdriver.js I can see the declaration of the FORCED_COMMIT_TIME variable, but I can't find where (or if) it's being utilized.

Hey Nathan! 

Are you seeing issues with the data your Rise 360 course is sending to your LMS? If you can tell me a little more about what you're seeing, I'll try and point you in the right direction!

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.)

Hey, Nathan! Our Support Engineers have a deeper knowledge on this topic, so I'm going to put you in touch with someone from that team! I've shared the latest information with them, and they'll reach out to you via email soon.

Hi, folks! I wanted to share an update for anyone following along in this discussion.

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.

If we get an update on this issue, we'll pass it along to you. Thanks for bringing this to our attention!

Hi Alyssa / Articulate, is there any further update on this please? We are experiencing issues with Rise's lack of automatically committing data as reported by Nathan above.