34 Replies
Karl Muller

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 

Alyssa Gomez

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!

RISE 1

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

Mark Murray

Hi Alyssa,

 

It sounds like we are seeing a different issue.  We are finding that Rise 360 and Storyboard courses hosted on Saba, are getting marked complete if a learner closes the Chrome content window.  When they choose the exit option within the content, it appears that the progress is being saved correctly.  It is only when they click the ‘X’ of the browser window that this happens.  We can recreate the issue this issue in Chrome v83, but it does not seem to happen in earlier versions.

Alyssa Gomez

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!

Jo Innes

Hello, just want to join in with this discussion as we are experiencing this problem as well.  When people have finished the e-learning they receive an error message that they have not met all the requirements of the course.  Our LMS is Successfactors.  We have also noticed something that Mark mentioned in a post above ("When they choose the exit option within the content, it appears that the progress is being saved correctly. It is only when they click the ‘X’ of the browser window that this happens.")

We have currently put a hold on all e-learning roll-outs and content import whilst we were trying to work out the problem but we actually need to roll out some material quite urgently so very much looking forward to hearing a solution.

Would advising all users to use Mozilla as their browser be a good temporary solution do you think? 

Alyssa Gomez

Hey folks,

Thanks for sharing what's going on with your Rise 360 content. We're having a look at this behavior, and we've seen that making this adjustment in Chrome 83 has helped in some LMS environments:

1. Open Chrome browser
2. Go to chrome://flags/#allow-sync-xhr-in-page-dismissal
3. Change the drop-down selection from "Default" or "Disabled" to "Enabled"

We'll let you know if we are able to make changes to Rise 360 output that would help.

SibaPrasad Padhi

We know this work around but this cannot be provided to 50K users internally and many users externally. This needs to be fixed at course level so that the pages can communicate both synchronous and asynchronous way with the LMS. Do we have a solution at rise during publishing level to select these 2 options during publishing SCORM/AICC output.

Jim Murtagh

We are optimistic that a Moodle revision to 3.7.6 may fix our issue (we are using 3.7.2). Testing on our development platform showed the problem resolved. Our next scheduled maintenance window on our production server is next week. I'll update when we see what happens.

This is the solution we are currently offering customers, and it has been working for them.

1. Open Chrome browser
2. Go to chrome://flags/#allow-sync-xhr-in-page-dismissal
3. Change the drop-down selection from "Default" or "Disabled" to "Enabled"