SCORM files are packaged in third-party authoring tools before being uploaded to Learnster. Issues can originate from the file itself or the authoring tool's export settings. Here's how to track down the cause. 🔧
ℹ️ Learnster supports uploading SCORM packages into a course. From there, we only receive a completion event sent by the SCORM file itself — we do not affect or manage ongoing progress within the SCORM. Tracking behaviour during the course is controlled entirely by the authoring tool's settings.
The SCORM file won't load at all
Check the file format. Learnster accepts .zip files packaged in SCORM 1.2. Make sure the file exported from your authoring tool is a valid SCORM 1.2 zip (not a raw folder).
Unpack and repack the zip. Extract the SCORM package and verify that the root of the folder contains an
imsmanifest.xmlfile. Then re-zip the contents and upload the fresh file. This often resolves issues caused by incorrect compression or folder structure.Re-upload the file. Open the SCORM activity in the course outline and use Edit content to re-upload. Sometimes a re-upload resolves a corrupted or incomplete initial upload.
Disable pop-up blockers. Some SCORM packages open in a new window or iframe. A pop-up blocker can silently prevent this. Ask the learner to allow pop-ups for their Learnster domain and try again.
SCORM loads but progress/completion isn't tracking
This is the most common SCORM issue and almost always originates in the authoring tool's export settings, not Learnster.
Check the completion trigger in your authoring tool. The tool must be set to report completion to the LMS. Common settings to look for:
Tracking → Complete when all slides viewed
Tracking → Complete when quiz score reaches X%
Report status to LMS: Passed / Completed
If this setting is missing or set to "None," Learnster will never receive a completion signal.
Try re-exporting as SCORM 1.2. Learnster supports SCORM 1.2. If your authoring tool exported a different version, re-export as SCORM 1.2 for best compatibility.
Check the SCORM activity settings in Studio. Open the SCORM activity and review its settings to confirm everything is configured as expected.
Test on a separate learner account. Go through the SCORM yourself on a test learner account to confirm whether the issue is with the file/settings or specific to one learner.
Contact the SCORM provider. If the above steps don't resolve the issue, reach out to the provider who created the SCORM file and share any error details or information about failing sessions. The root cause is usually in the SCORM package's configuration, which only the content creator can address.
Progress was tracking before, but has stopped for existing learners
If the SCORM worked previously and has stopped, the most likely causes are:
The SCORM file was replaced with a new version. Existing learner progress may not carry over depending on the tracking method. See Upload of External Course History if you need to import historical progress.
The SCORM package itself may have changed how it reports completion. Contact the provider to check whether a recent update to the content changed the completion trigger.
Related Articles