This article explains why progress may not save correctly in SCORM packages hosted in TalentLMS and what to check when Learners are unable to resume where they left off or are not seeing their progress reflected in the course.

How progress is usually saved

SCORM content typically saves progress through its runtime data model, using fields such as lesson status and suspend data to preserve in-progress activity between sessions. In practice, this means resume behavior often depends on the package saving and restoring the correct location.

Why progress may not save

• Learner exited before the content finished saving: A very common cause is leaving the unit before the content finishes sending its final progress update. In SCORM, this can happen when the package writes state only at certain points, such as when the learner reaches a checkpoint, uses a final navigation control, or exits the unit properly. If the learner closes the content too early, the latest progress may not be preserved.
• The package was not authored to store resume data reliably: If a learner can open a unit but always starts from the beginning, the package may not be saving resume information consistently. In SCORM, that often points to suspend data or lesson status not being used as expected.
• Browser, device, or session interruptions broke the communication: Progress tracking depends on uninterrupted communication between the content and the LMS. If the learner switches apps, closes the browser, loses connectivity, or the browser blocks part of the communication flow, progress may not be saved. This risk is generally higher on mobile devices and in environments where the browser or OS aggressively suspends background activity.

The issue is in the package, not in TalentLMS: If the same package fails to save progress consistently across environments, the root cause is often the content itself. This is especially likely when the package is not sending the expected SCORM runtime values at the right moment. If the authoring logic does not save state cleanly, the LMS cannot reconstruct the learner’s resume point on the next launch.

What should you try?

When troubleshooting, learners should complete the unit in one uninterrupted session whenever possible. They should avoid closing the tab or window early, switching apps, locking the device, or changing networks while the content is open. If the course includes an Exit, Finish, or similar control, they should use it rather than simply closing the browser. These steps reduce the chance that the final progress update will be lost before it is stored.

If the learner returns and the unit has not resumed properly, they should reopen the content and check whether it offers a resume option. If it does not, or if it always restarts from the beginning, that suggests the package did not restore the previously saved state. In that case, the issue is likely related to the content configuration or to how the previous session ended.

Additional checks you can do

For more on related SCORM behavior, see: Why your SCORM content may not complete in TalentLMS.

Try to reproduce the issue with a test user and note exactly where progress stops being preserved. If learners lose progress after a specific screen, after closing a pop-up, or only when resuming on a different browser or device, look for a pattern. It can reveal whether the issue is tied to authoring logic, a browser condition, or the way the session ends.

For SCORM content, you can also review the status values the package sends back to the LMS. These values show whether the content is correctly reporting learner progress. If the package sends cmi.core.lesson_status = completed or passed and commits the data successfully, the LMS should be able to record the learner’s result. If the package only sends incomplete or never sends a final status value, the issue is likely in the package configuration and should be reviewed in the authoring tool.

If the package was recently updated, check whether resume data should be reset. Old suspend data may no longer match the updated structure of the course. Resetting bookmarks can resolve broken resume behavior, though it also means in-progress learners may need to start over inside the package.

If the problem persists, test the content outside the affected portal, for example, in a validation tool such as SCORM Cloud. If progress fails there as well, the strongest next step is to review the package settings in the authoring tool, because the issue is likely in how the content saves and reports state.

When to involve the authoring tool

You should refer the package back to the authoring tool when:

• Progress is not being saved even though learners are following the expected flow
• The issue reproduces consistently across environments
• The package fails after an update

Still not working?
If progress still does not save, contact our support team and share:

• Course name
• Unit name
• Affected users
• Device or browser used
• Whether this happens for all learners or only some
• Whether the content was recently updated

If needed, the package can be tested to confirm whether the problem is caused by session handling or by the way the content was authored to report progress.