Go.Learn not capturing SCORM progress

My users are experiencing this now! What a waste of time.

I am opening a ticket.  

Issue- Many of my users have lost their progress in the go.learn app.  It is not writing back their progress in SCORM courses, whether downloaded or not.  The enrollment status shows as in progress (both in app and browser), but there is no way to resume back to their last spot in the SCORM using the app (or browser). Upon launch, it takes them back to the beginning in either.

The SCORM works fine in a browser for stopping and resuming all in the browser.  If a user starts a course in the browser, then goes to resume in the app, it DOES properly resume. 

If a user starts a course in the browser, resumes in the app, continues in the app, exits, and then resumes again in the app, it also does seem to properly resume.

Hi ​@Lisa C. - I just came across this post and see that you were having this issue recently (6 months ago).

Seeing as I am now starting to experience this exact phenomenon, was wondering if you could share the outcome of your ticket with docebo, or better yet, how you were able to fix this?

Hey ​@TmunozBDS 

I did not get a good answer on this.  I am using a lot of content from Marcom via the Content Marketplace/go1.  Those SCORMS seem to be finicky- the user has to close the course with the little, hidden red x in the player, not either one of the Xs in the course player or SCORM loader window.  This seems horribly incompatible, and it’s unreasonable to expect an average user (especially frontline workers) to close out of a course like that.  Now that Marcom is no longer a go1/Docebo content partner, it won’t be an issue.  However, now my problem is replacing all that content…  

For other content providers/SCORM files, I haven’t heard of this issue lately (no one has been complaining directly to me).  I also have not revisited testing/troubleshooting.  I would like to hear more about your experience with this issue.

Hi everyone, there is some info about SCORM completion tracking on the Go.Learn app, including the issue with “finicky Xs”, in this KB article:  
https://help.docebo.com/hc/en-us/articles/360020124279-Go-Learn-App-Info-and-Limitations#:~:text=Completion%20tracking%3A,be%20correctly%20tracked

Thank you for the response, ​@Lisa C.

We started experiencing this issue on 1/30/25 and quickly reported to docebo same day.
I made sure to test this issue with a SCORM 1.2, a SCORM 2004 Version 4 (thinking the issue was with SCORM 1.2 which it wasn’t) and xAPI file, confirming that it was just SCORM as xAPI tracked correctly.

These files were all tested on both Apple and Android devices 

Remembering that there had been a recent update to the Go.Learn at that time (1/20/25), I figured it was tied to that specific update as this was not an issue prior to that going live. Free Tip: Docebo’s Product updates – Docebo Help & Support compilation of updates is my go-to.

We ended up escalating this our CSM who informed us that the next Go.Learn update would resolve our issue (1/3/25) which thankfully it did. I just wish docebo had a dedicated Go.Learn app updates page that dives deeper into what has actually been addressed and/or updated.
 

Good afternoon. One of things I do know is that SCORM becomes extremely finicky when it comes to using mobile browsers.

Lets say that the dedicated app helps with responsive design and how the widgets show themselves for a person versus a browser session attempting to render it correctly. And maybe your design choices in terms of page management and navigation to courses.

After telling my 1% of my targeted audience that had an issue with the course and the person losing their course session or the mobile device terminating the session and the course is still active (because it was downloaded to the mobile device) my basic understanding when SCORM was implemented way back when? Is that it counts on a constant communication with the LMS.

xAPI was supposed to relax this...allowing for more shorter bursts of information between the course and the learning record store. An analogy - You could go into that tunnel and come back out on the other end and continue your course.

All of that said - I have passed along this advice to others in the past. When you have an aspecific issue with your course and triggering completion criteria? The better thing to do is to test/test/test so that you can isolate your issues to potentially a browser, OS, and device.

You can share what the course is doing in debug mode with the service desk and see if they can be a hand with what you are encountering. This may be a first step when you draw blanks.

Try testing outside the LMS - in a review type of setup (Articulate Review and other products support this) before deploying. If you are stuck for a platform? Try your course in SCORM Cloud.

You can setup a small free account to test out your logic.

And more importantly? If you are seriously going to try to debug your course and you are drawing only question marks compared to spades (sorry about the card metaphor) and have even lost your patience with user support? I would suggest to reach out Rustici Software….those folk helped to work on aspects of SCORM way back when. The dont charge for the review or anything like that.

Now - if there is an issue with the Learn app, that is a different story….but I figure take a moment and comment on your comment….it is pretty real what you are encountering - and part of that is because of the aged approach.

Thanks for all the added insights. Yeah, it seemed like xAPI was supposed to be the way to go, but content providers are still sticking with SCORM files.  Unfortunately, this is such a PITA, as I rely heavily on the mish-mosh smorgasbord in go1/Content Marketplace for 95% of my content.