With the May 2026 release, the behaviour of the SCORM tracking option of Advanced eLearning course types changes. If you manage eLearning courses with SCORM, xAPI or cmi5 content, read this article to understand how the update may affect your existing courses.

What changes

Real SCORM, xAPI (Tin Can) and cmi5 packages (.zip files with their own completion manifest inside) are now uploaded and tracked on SCORM Cloud always, regardless of how the course type tracking option is set. This is because these packages can only be run inside SCORM Cloud: without the upload they could not be consumed correctly.

The tracking option keeps controlling the behaviour of the other content (PDF, MP4, MP3 and URL links):

• Option enabled — non-SCORM content is packaged as SCORM and uploaded to SCORM Cloud to allow automatic tracking of consumption (progress, time, completion).
• Option disabled — non-SCORM content is delivered directly, without wrapping on SCORM Cloud. In this mode the lesson completion is detected only when the employee has consumed all the content (all pages of the PDF, 100% of the video) or when the employee confirms it manually with the Mark as complete button.

Previous behaviour

Before this release, when the option was disabled no content was uploaded to SCORM Cloud, including real SCORM/xAPI/cmi5 packages. In practice, in that configuration the SCORM packages were unusable, because they lacked the runtime needed for consumption.

Impact on existing courses

If you manage advanced eLearning courses with the tracking option currently disabled that contain lessons with real SCORM, xAPI or cmi5 packages:

• from the next consumption, those packages will start being uploaded to SCORM Cloud and consuming Cloud registrations, even if the course type option stays disabled;
• the non-SCORM content (PDF, MP4, URL links) in the same courses will keep behaving as before — no upload to the Cloud, manual or automatic completion within the platform.

If you want to keep uploading nothing to SCORM Cloud for these courses, you need to remove or replace the SCORM/xAPI/cmi5 packages from the affected lessons. If instead you want to enable automatic tracking of the non-SCORM content as well, just enable the tracking option in the course type.

Why we changed it

The previous behaviour produced an effectively unusable configuration: SCORM packages without their own runtime cannot be run, so they were not delivered to employees in any way. Narrowing the meaning of the option to only the content for which it makes sense (PDF, MP4, MP3, URL — the content that can be automatically converted to SCORM) removes the ambiguous configuration and makes Cloud registration usage predictable.