Some SCORM related issues might be caused by suspend data, such as the following:
Altering an existing SCORM course causes data errors
A SCORM course holds data about a user's progression and when it loads, it validates this data against the imsmanifest.xml file. If the data does not match, an error will occur. For example, if you originally had 14 slides in a SCORM course and you remove 1 slide, the data will no longer match, as the expectation is, there are 14 slides in the SCORM course.
...
If you do choose to overwrite a SCORM course, then you can select the relevant option in Articulate Storyline and other WYSIWYG authoring tools, which ignores suspend data. This ensures that there are no issues when uploading a new version of a SCORM file, but it means that the users who are currently in progress must restart the SCORM course.
Users cannot progress or complete a SCORM course
Suspend_data is used to store temporary information about a SCORM course, such as:
How much progress a user has made
Any assessment/quiz results
If a user has completed the SCORM course
For more experienced developers, suspend_data can be used to store more granular information about the status of a SCORM course.
Fuse supports SCORM 1.2, which allows up to 4,096 characters in the suspend_data variable. If the course tries to write more than this, issues related to the loading or completion of SCORM courses can occur. As this is standard, there is nothing that Fuse can do to resolve this.
To resolve these issues:
If you have developed the SCORM course internally then changes can be made in-house. We strongly advise that you break larger SCORM courses into smaller chunks or disable the resume functionality.
If the SCORM course comes from an external supplier, we recommend contacting them, as the SCORM course is not designed to work with SCORM 1.2 and the supplier must make the necessary changes for you.