Forum Discussion
SCORM 2004 3rd and 4th Edition Error in Cornerstone OnDemand
Is there any solution for this yet in Rise? Is there an answer to EvelynHillmon question above about why multiple messages are sent so rapidly?
Hi CristianaRat103! I was looking at the previous case to see what our Support Engineer recommended, and wanted to share those recommendations below:
- Clear your cache or cookies
- Test in a private window
- Open Chrome in Incognito mode and see if the issue still happens.
- Try a different browser
- If you're using Edge with extensions, they can sometimes affect behavior. Testing in Chrome can help rule that out.
If it works in SCORM Cloud but not in your LMS, it may be LMS-specific. In that case, we recommend reaching out to the Cornerstone Support team so they can take a closer look. Let us know what you find!
Is there an answer to EvelynHillmon question above about why multiple messages are sent so rapidly?
Hi CristianaRat103,
Happy to jump in here!
The rapid sending of bookmarking and other data is likely an LMS-side handling issue, during the exit flow of the SCORM package itself. Which is expected behavior for SCORM content. This exit flow usually includes saving any pending runtime values before ending the session. The 'Exit Course' action issues the LMS's 'terminate call', and may also attempt to close the course window depending on how the LMS launched the content.
Multiple sends can occur when:
- The course may set several runtime values in quick succession upon exit, such as location/bookmark, status, and session time.
- The driver may commit more than once while flushing pending changes before terminating the session.
Seeing multiple bookmarks or data transmissions within milliseconds is generally expected and part of the normal SCORM "save-and-terminate" sequence.
Moving forward, I suggest first testing the published output in SCORM Cloud. If the course exits, bookmarks, and completes normally there, it strongly indicates that Cornerstone is the source of the error rather than the Rise content. Also, enabling debug mode in the LMS will allow you to see exactly what data is being sent during the 'Exit' process. As well as confirm whether the course is setting values and terminating correctly.
Since the 'Exit' process may attempt to close the course window, the final behavior can depend on how the course is launched and what CSOD expects after termination. An LMS administrator should be able to address any adjustments required by the specific LMS environment.
