Timeout issue

Hi, I'm hoping I can get some help with the way Storyline 2 communicates with our LMS...

I have a module that times out to about 35 minutes (not counting the quiz), and it's in "Restricted" mode so that the user can't skip any content and go straight to the quiz (not my call). The LMS is timing out at 30 minutes because it's not receiving any info from the module that the user is active. This happened to one user who had to back all the way out of the LMS, log back in, and start the module again. When she did, there was no evidence that she'd gone through part of the module, and she had to start over. When I went through it on the LMS I got kicked out, but was able to resume the course where I'd left off.

Can anyone tell me a quick/easy way to report to the LMS that the user is active? It doesn't need to be every slide (and because it's 240 slides long, that wouldn't be the best way to remedy the problem). I have it set up so that it reports the quiz score to the LMS; would it make any difference to report the slide progress to the LMS instead?

I just need a way to ping the LMS periodically and let it know that the session is still active. I'd appreciate any help you might be able to give.

 

 

12 Replies
Justin Grenier

Hey, Sean!

Storyline 2 will send a keep-alive message to the LMS every 10 minutes by default, and this keep-alive message includes Suspend Data that will help the LMS recover from a learner's session that has been suspended for any reason.  A great way to verify that this keep-alive message is happening is to enable LMS Debug Mode so that you can watch the communication flowing across the wire.

Although we can't support the modification of published output, Gerry hints here at how you might go about modifying the frequency of that keep-alive message.

You'll also find another conversation here on how you might configure a JavaScript Trigger to invoke an LMSCommit() upon the load of every slide, but this feels like overkill to me, and Storyline's default keep-alive message should be more than enough.

I'd recommend enabling LMS Debug Mode and using the resulting debug log to show the keep-alive message to your LMS Admin.  If you need any help interpreting those logs, please feel free to send us a copy for a closer look.

Please let us know if you need anything else, and have a great day!

Jason Lampitt

Hi Justin,

In Storyline 360, we've been experiencing the keep-alive event every minute. I checked the ForceCommit interval in lms.js and the value is still 600,000 (milliseconds), as was in prior versions of Articulate Studio and earlier versions of Storyline.

Any ideas what would cause the ForceCommit function to fire every minute (60,000 milliseconds) from a Storyline 360 course?

Ashley Terwilliger

Hi Jason, 

Thanks for reaching out here! Our team also saw the same thing, and we've filed this as a possible bug as the HTML5 LMS output is sending a status to the LMS even if we set var FORCED_COMMIT_TIME = from 60000 to 0. 

We'll let you know here as soon as this is fixed, and it's currently targetted for the next update of Storyline 360. 

Crystal Horn

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

One of the fixes addresses an issue where in the HTML5 output, data is sent to the LMS every 60 seconds even if set not to.

Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!