SCORM File Issue - Worked in LMS for Months, Now Suddenly Stopped Working

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:

1. 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.
2. 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.
3. 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.