Forum Discussion
SCORM File Issue - Worked in LMS for Months, Now Suddenly Stopped Working
Hi Friends,
I use Docebo and my SCORM files usually work great on their platform.
We started noticing new hires were not able to get to the final score slide in their training. They can only get to the congratulations page if they get all the questions right. Once they get to this page it gets stuck loading and learners are not able to click the next arrow to get to the score page.
I played with the file in Storyline and re-uploaded it in hopes that would fix the issue, but sadly after taking the course again it's still malfunctioning.
I put the SCORM file into SCORM Cloud (a new tool I just discovered and am not sure how to use quite yet). This is the URL to what they discovered when I took the course when it got stuck again: https://app.cloud.scorm.com/sc/guest/ViewDebugLog?logId=759bcc6d-933d-4203-8ea6-1427934c5ef1&courseTitle=OSHA-HazCom+-
I'm not sure if any of that info in the URL above is helpful. I'm not really understanding it.
Has anyone else had experience with a SCORM file failing a year after uploading to the LMS and freezing/loading on the slide before the last slide so the course does not record on the LMS.
Thank you for your help!
Hi there KatieKarkowski the log does point to an issue. The data that is stored on the LMS so that a state can be persisted can only have a maximum length of 4,096 characters. The string that your course is attempting to store in this instance is 4,135 characters, which causes the data not to be stored, and will affect users in that the course will stop storing "resume" data once the string exceeds 4,096 characters. I haven't seen this break a course in this way before, and so it might be a red herring, but what you do see with this error, is a point at which the course can no longer resume the user at the point at which they left off. The user will always be returned to the point where the resume data last successfully was able to be stored.
This can happen when a course has multiple slides configured to "resume" rather than "reset to initial". It can also happen, quite quickly, if a quiz is also set to be resumed.
There are a couple of options to resolve this:
- If the LMS supports SCORM 2004 3rd or 4th edition, use this, as the database field used to store resume data allows over 70,000 characters rather than 4,096.
- Look for opportunities in the course to remove "resume" from slides that do not need it. For every slide that is set to "resume", data needs to be stored so it can be returned to the state it was left at.
- Split the course into different modules if there is an opportunity to.
The odd thing about this, is the issue should have always existed, but may not have been triggered by everybody, as the amount of data stored to resume can differ depending on where the user exited the module.
The issue you are experiencing with the freezing, I'd like to take a look at if possible, or you may have to work directly with Articulate staff so you can share your file with them privately.
I completely agree with Sam. The SCORM 1.2 error 405 regarding cmi.core.suspend_data exceeding the limit indicates that the LMS cannot save the current session's progress, but it should not prevent the learner from continuing the course in the current session. However, any progress made after the error occurs will not be saved to the LMS. When the learner relaunches the course, it will resume from the last successfully saved state, which could be a previous slide or activity. However, any truncation or failure to save this data could result in the course freezing or loading incorrectly upon reentry.
I believe that even if the course is published in SCORM 2004 to eliminate the suspend_data limit issue, the freezing issue may still persist.
