Internet Connectivity - Problems with SCORM Cloud

Hi Neil,

I can't say that I've seen that behavior before, but I'm wondering if you've looked into this method here to let the user know that their connection has been lost and after enabling this feature, users will be alerted that their data cannot be committed to the LMS if an error occurs when the content is attempting to save their data to the LMS.

Hi Ashley,

Thanks, for this unfortunately this solution does not work for TIN CAN API. Is there any solution similar to this that would work for TIN CAN API? 

Please get back to me when you can.

Many Thanks

Neil Chandarana

Hi Neil,

I checked in with a colleague of mine for a bit further explanation. When a learner resumes a course that has been suspended previously, we ask the LMS to send us suspend_data that tells us where the learner left off on their previous attempt.  If the LMS is unable to send us this suspend data for some reason, we will assume that the learner is starting over from scratch, and yes, we will definitely send new suspend_data to them LMS at the end of the learner's second attempt, and this suspend_data will overwrite the original suspend_data.  This is by design, and there is no workaround that will cause us to *not* send new suspend_data to the LMS. If you'd like to see something to prevent that behavior I'd ask that you share your thoughts in the form of a feature request with our development team. 

Hi Ashley, 

Was there a resolution for this, we are having the same issue.

Thanks

Katie

Hi Katie,

Are you looking for information about how to *not* send the resume data? This hasn't changed in Storyline 3 or 360. Could you tell us a bit more about what you're looking to accomplish and I can look for other ideas that may help! 

Hi Ashley,

Thanks for getting back to me.

We have exactly the same issue as Neil described above. With Tin Can the course communicates with the LRS. When the course sends a request to the LRS asking for the stored state, if some reason there is a connection error and the course does not get the response from the LRS, the user is taken back to the start of the course. If the user then presses 'Next', their new progress is stored.

When the course player asks for the state, we would like the player to only accept the response as valid if it has HTTP status 200 OK or 404 Not Found. If there is any other HTTP response status and therefore an error, we would like the course to ask for the data again.

We have a long course and this is a common issue for our users, do you know if there is a way for us to make the course perform a get request on the state more than once?

Thanks,

Katie

Hi Katie, 

It may be something that you could send more frequently or on demand using Javascript or other custom code, but that's all beyond my expertise or what I can provide help for. The behavior as described before still holds true in Storyline though.

Ok, Thanks.

I will put a requests in with the Articulate development team.

Hi, Katie. I know this post is two years old and am hoping for an update. Your original suggestion references this link.  Its great information, except Flash, is dead on the vine.

 

Any updates for how to do this with HTML5?

Hello there, Robbie!

We've still got our eye on this feature, and will definitely let you know if there's any forward movement on the same functionality for HTML5. You'll be notified immediately since you're now subscribed to this discussion.

Thank you for adding your voice!