Tracking issues while using Google Chrome

Hi Cristina, the forum post you found is a couple of years old. I haven't had any issues with SCORM modules tracking in the LMS or heard of any recently.

How confident are you that this is not a problem with the LMS? It is possible there has been a change on the LMS side.

I would recommend testing your modules on SCORM Cloud (a free platform) and confirming if the modules do or don't have the same issue. You can at least then determine if the issue is from the content or browser side, or with the LMS that the content is running on.

Hi Cristina,

It looks like Sam has you pointed in the right direction, but I wanted to add a few other thoughts! 

I'd start by checking what update of Chrome and Storyline you're using and ensuring it's the latest possible. Storyline 360, build 3.43.22859.0 is the latest version, and you can update directly from the Articulate 360 Desktop App. 

Also, if you test at SCORM Cloud and you still have trouble, our Support Team is standing by 24/7 to help. You can use that link to connect with them directly. 

Hi Sam!

Thank you for your reply!
Is LMSCommit(); working then? Do you know exactly what Javascript code I should use to force bookmarking?

Anyway, we tested our module on SCORM Cloud as suggested and it seems to be working just fine. We'll try and check with our LMS support to see if there has been any change while waiting for your reply.

Thanks again!

Hi Ashley!

Sorry I missed your reply!
I've already checked and both Storyline and Chrome are up to date.

No apologies necessary, Cristina! Glad to hear you're on the latest update and that SCORM Cloud worked well. Let us know if your LMS provides any push back, and our Support Team can offer you some ideas and strategies on how to share more "evidence" with them that the course is working fine!

One initial idea is to look at the data being set in LMS debug mode and share the results from SCORM Cloud and your LMS with the LMS team.

Hi Cristina, LMSComit("") is working. You don't need to add any JavaScript to control the SCORM API unless you are doing anything outside of what Storyline does already. It takes care of all of the SCORM API communications for you. 

Good luck with your LMS team. As Ashley mentioned, gather your evidence as it is quite common to get immediate push back before they investigate. However, if you gather your evidence (SCORM Cloud log files are good) you stand a good chance of a quicker resolution.

Hi,

Thank you so much again for your replies!
Our LMS team is working into fixing the Chrome issue.

As for the LMSCommit(""), we'd like to know if there's a way to force the communication between the module and the LMS in specific events or moments during the course.

As of now, our LMS tracks the progress of the course only after jumping to the next slide, so if hypothetically there were a power shortage while in the middle of a slide, the user would lose the progress on that specific slide and would be forced to play that same slide again from the start when re-entering the course.

Is there any Javascript we could add to manually bookmark the progress of the user in the middle of a single slide?

Hi Cristina, I have looked into this before, and could not find a solution. I don't think the method to send all cached data is a public one and so it will have to be a slide navigation that triggers the save. It is only one slides worth of data the user will be losing, and so the risk is quite small and I think will not cause a great number of support calls.