Chrome v83

Hi,

As from Chrome Version 80 and later, depending on the LMS you are using, you could experience the issues you have described. 

The short version: it's a communication issue between Chrome and the LMS as a result of changes to Chrome V80 and higher. See: https://www.chromestatus.com/feature/4664843055398912 

There are several threads about this topic. Here is one: https://community.articulate.com/discussions/articulate-storyline/chrome-80-update?page=2 

Hello! Thanks for giving us a heads up.

I tested a sample course in SCORM Cloud using Chrome 83, and it looks like the course data is saved even if the learner closes the browser window. You can also test my sample course by clicking here. 

Have you tested your own course in SCORM Cloud yet?  If so, are you getting the same results? We generally compare the behavior in SCORM Cloud to your LMS experience to try to parse out Rise 360 issues versus LMS issues.  We are happy to help you with that testing if you'd like to share your output file!

Hello again, and thank you for your answers. v80 worked fine for us, the problem started a week ago with the v83.

Yesterday, we uploaded a course in a Moodle fresh install, and this was the Moodle report in debug mode when you close the browser window -something that students do often:

Wed, 27 May 2020 06:50:56 GMT: LMSGetValue("cmi.core.lesson_status") - incomplete => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSSetValue("cmi.core.session_time", "0000:00:21.26") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSSetValue("cmi.core.exit", "suspend") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: Commit("", "") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSCommit("AJAXResult", "false") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSCommit("result", "false") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSCommit("errorCode", "101") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSGetErrorString("101", "General exception") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSGetDiagnostic("101", "101") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSFinish("AJAXResult", "false") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSFinish("result", "false") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSFinish("", "") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSGetErrorString("101", "General exception") => 0 scoid = 1428
Wed, 27 May 2020 06:50:56 GMT: LMSGetDiagnostic("101", "101") => 0 scoid = 1428

I guess this is more useful than sharing the course itself, but anything you need, just ask :)

Thanks, Rise1! I'm going to share all of this information with our Support Engineers. They'll reach out to you soon with next steps!

Thank you very much, as always! :D

Thank you!  Please be sure to post your findings here as well.  I believe we are running into the same issue.

Hi Mark,

We're finding that Rise 360 courses hosted on Moodle do not resume properly in Chrome 83. Instead, courses always start over from the beginning. Is that what you're seeing, too?

Thanks for those details, Mark. I'd like to enlist the help of our Support Engineers to take a closer look at what you're seeing. I've opened a case for you, so you'll hear back from the team soon!

Hello, is there an update on this, please. We have a lot of users that this is affecting.

Hi folks! I wanted to jump on here and clarify a couple of points:

• We are seeing an issue where Rise 360 courses hosted on Moodle do not resume properly in Chrome 83. Instead, courses always start over from the beginning. We have logged this as a software bug.
• The issue Mark was seeing in SABA LMS was not found to be a bug. Instead, the problem Mark is encountering is a possible issue with Saba LMS when used with the latest Google Chrome update.

If you're unsure if your courses are affected by the Rise 360 bug or an LMS issue, please send your SCORM output file to our team by clicking here. We'll test it from our side to confirm!

EDIT: Here's another recent discussion about SABA settings that should help!