Timeout issue

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!

Hey Justin,

Thanks for the info! So either the keep-alive message isn't getting sent, or the LMS isn't reading it. Is there a menu setting to disable the keep-alive message? If so, I'd like to check to make sure I didn't disable it by mistake.

No, I'm not aware of a way to disable the keep-alive message without manually editing the lms.js file in the published LMS output.  It should just work!

Good to know! Thanks.

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?

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. 

Hi Ashley,

I'm glad you were able to validate my observations! Will look forward to the next update of Storyline 360.

No problem, Jason! I'll let you know as soon as the update is ready here. Thanks for your patience while my team works on this one. 🙂

Is there a timeout function in Storyline 3 as well? If so, does the keep-alive message come up after 10 minutes, like in SL2? Trying to figure out whether it's worth it to use the restricted mode.

Thanks.

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!

Hi Crystal, any idea when SL3 will have this update?

Hi Dave, 

Great question - Storyline 3 receives updates less often than Storyline 360. Not to worry, as any bug fixes released in Storyline 360 will make it's way to Storyline 3. Once we have a release date for that, we'll let you know here.