All articles
SCORM TroubleshootingLMSAuthoring Tools

SCORM Completion Not Recording in Some LMSs but Working in Others? Here's Why

When one Storyline course completes in some client LMSs but not others, the cause is usually exit handling or the SCORM status model. How to find which, and fix it.

LI
Larry Ioannidis
16 November 20266 min read

Short answer: when the same SCORM course records completion in some LMSs and not others, the course is usually fine, and the difference is in what each LMS saves and reads. There are two common causes. Either the learner leaves before the course's final data reaches the LMS, or the status the course reports doesn't match the status the LMS looks for. Test the course in SCORM Cloud, then in the LMS where it fails, and compare the SCORM calls in each.

A training provider came to me with this: one Storyline course, shipped to many client LMSs, that recorded completion in some of them and not in others.

Why it happens

The final save doesn't happen. A SCORM course sets values as the learner works through it, then calls LMSCommit (SCORM 1.2) or Commit (SCORM 2004) to ask the LMS to save them, and LMSFinish or Terminate to end the session. A course doesn't have to call Commit, but when it does, the LMS must save any pending data, and finishing the session saves it too. Between those calls, LMSs differ: some send data to their server as each value is set, others wait for commit or finish. If the learner closes the tab or the LMS window, the finish call may not run, or may not reach the server. In the first kind of LMS that's harmless; in the second, the completion is lost. Browsers have also tightened what a page can do while it's closing, which affects LMSs that try to save at that moment.

The status doesn't match what the LMS reads. SCORM 1.2 has one field, cmi.core.lesson_status, holding passed, failed, completed, incomplete, browsed or not attempted. SCORM 2004 splits it in two:

SCORM 1.2SCORM 2004
Status fieldscmi.core.lesson_status (one field)cmi.completion_status (completed, incomplete, not attempted, unknown) and cmi.success_status (passed, failed, unknown)
A typical mismatchThe LMS only counts completed; the course sends passedThe LMS reads only one of the two fields, so a learner who passed can still show as incomplete

Storyline chooses which values to send from its publish settings: Report status to LMS as (Passed/Incomplete, Passed/Failed, Completed/Incomplete or Completed/Failed) and what it tracks completion by (slides viewed, a quiz result, or a completion trigger). A setting that suits one client's LMS can look wrong in another.

The LMS has its own completion rules. Some LMSs only mark content complete once the learner exits it, or apply their own completion settings on top of what the course reports. Workday Learning, for example, relies on the package to send its completion status, recommends sending it as early as makes sense, and has its own "completion without exit" tracking logic.

How to fix it

  1. Reproduce it in SCORM Cloud first. If completion records there, the course logic is probably sound and the difference is in the LMS. If it doesn't record there either, start with the course-side causes in Common SCORM Errors.
  2. Set completion before the learner can leave. Mark the course complete on the last content slide or the results slide, not on the exit button, then commit it and check the call returned true, so the status is saved before anyone can close the window. In Storyline, that means tracking by quiz result or slides viewed, or a completion trigger on an earlier slide.
  3. Give learners a proper way out. Storyline's Exit course trigger ends the SCORM session properly. Put it on a clear button and tell learners to use it rather than closing the tab.
  4. Match the reported status to each LMS. Ask each client which status their LMS treats as finished. If most want "completed", report Completed/Incomplete or Completed/Failed. If pass/fail matters, check that their LMS counts "passed" as complete.
  5. Check the slides-viewed count. If you track by slides viewed, make sure the number doesn't include slides some learners never see, such as other branches of a scenario.
  6. Review the LMS settings with the client's administrator. Look at completion rules, how the LMS launches content (new window or frame), and options like Workday's completion-without-exit logic.
  7. Keep a record of which client has which build. If some clients need SCORM 2004 and others SCORM 1.2, publish both from the same source file and note who has which, so a fix reaches everyone.

How I'd check it

I run the course in SCORM Cloud and in SCORM Lab, my in-browser SCORM debugger, which shows every call the course makes to the LMS, in order. I note exactly which status values are set, and when commit and finish are called. Then I take the same package into the failing LMS with a test account and try every way out: the exit button, closing the tab, closing the LMS window, and leaving it until the session times out. Comparing what the course sent with what the LMS recorded usually points to one of the causes above. If you ship one course to a lot of client LMSs, my SCORM support desk and testing service are set up for exactly this.

Frequently Asked Questions

Why does my SCORM course complete in SCORM Cloud but not in my LMS?

If completion records in SCORM Cloud, the course is usually sending the right calls. The difference is normally in the LMS: when it saves data, which status field it reads, and any completion rules of its own. Compare SCORM Cloud's debug log with what the LMS recorded for the same run.

Does closing the browser window stop SCORM completion recording?

It can. If the LMS only saves data when the course commits or finishes, closing the window before those calls reach the server can lose the completion. Setting completion earlier in the course and giving learners an exit button avoids most of it.

Should a Storyline course for many different LMSs be SCORM 1.2 or SCORM 2004?

SCORM 1.2 is the safer default because nearly every LMS supports it. Use SCORM 2004 for clients who need completion and pass/fail reported separately, or more room for resume data, and test it in their LMS first. My SCORM 1.2 vs 2004 guide goes into the trade-offs.

Which Storyline 'Report status to LMS as' setting should I use?

The one that matches what each client's LMS counts as finished. Completed/Incomplete is often the safest choice when an LMS only looks for "completed". Passed/Failed makes sense where the pass mark matters and the LMS treats "passed" as complete. Ask the client or check their LMS documentation.

Can I fix it without republishing the course?

Sometimes. If the cause is an LMS setting, such as its completion rules or how it launches content, the client's administrator can change it. If the course reports the wrong status or sets completion too late, you will need to republish.

If one or two client LMSs are refusing to record completion, send me the details or book a call, and I'll find out which side the problem is on.

Tagged:SCORM TroubleshootingLMSAuthoring Tools

Need Help With SCORM?

Whether you're building your first course or troubleshooting a tricky LMS issue, I'm here to help. Get a free consultation — no strings attached.

Free 30-min consultation Same-day response No obligation