Docebo not completing a Storyline or Rise course

Fix it in Storyline, Rise or Captivate

1. Storyline

   Add an Exit button to the last slide with an “Exit course” trigger. Some browsers won't let a course close a window the LMS opened, so also tell learners on that slide to close the window after pressing it.

2. Rise

   Open Publish → LMS and turn on “Exit Course Link”.

3. Captivate

   Add a button on the last slide that exits the course.

4. Check the version

   Publish as SCORM 1.2 or SCORM 2004 3rd Edition. In Storyline, that is “Report to an LMS” on the LMS tab of Publish → LMS / LRS → Reporting and Tracking; in Rise, the “LMS” drop-down under Publish → LMS.

5. Republish and check again

   Drop the new zip into Alder, repeat the test run with the exit button, and check that “Finished?” says Yes. Then test one learner in Docebo before rollout.

Version, score and size

• The SCORM version. Docebo's documentation lists SCORM 1.2 and SCORM 2004 3rd Edition. A SCORM 2004 4th Edition package may still work, but Docebo doesn't promise it.
• The score. For SCORM 2004, Docebo reads the points score (cmi.score.raw), not the percentage (cmi.score.scaled). A course that sends only the percentage shows no score in Docebo.
• The size. Docebo refuses SCORM packages over 1,024 MB.

Check the zip before you upload it again (free)

The test player and every check below are free. What you get with Pro is Alder's Docebo notes; more on that after the steps.

1. Drop the zip and pick Docebo

   Open Alder, drop the published zip (it is read in your browser; nothing is uploaded) and choose Docebo under “Uploading to”. A package over Docebo's 1,024 MB limit shows as a blocker on every plan. Any other Docebo note is counted, so you know it is there.

   

2. Finish the course the way learners should

   Click “Launch the course”, go through it, and press the course's own exit button on the last screen. Then click “I'm done”.

3. Read what an LMS would record

   “Finished?” should say Yes. If the course never ended its session, the findings include “The course never told the LMS it was finished” (RUNTIME-003, free): the exit button doesn't finish the course, which is exactly what Docebo needs. Docebo's dot shows whether it would record the session the way SCORM Cloud does.

   

4. Check what a closed window would lose

   Look under “good to know” for “The course only saves when it finishes” (RUNTIME-004). It means the course saves nothing until the exit button is pressed, so a learner who closes the window first loses the whole session.

What's free and what's Pro for Docebo

• Free: every check, the test player and its plain-English log, what an LMS would record, Docebo's same-or-differs dot, the report, every fix step, and the Docebo size blocker.
• Pro: Alder's other Docebo notes (the Close button, SCORM 2004 4th Edition, a percentage-only score) and the “Why?” behind each LMS dot. This page gives you the same facts, from Docebo's own documentation, so you can check them by hand.

In Docebo itself

Docebo's debugging article describes an option for superadmins, “Enable debug for SCORM API”, in the SCORM section of the advanced settings. With it on, the course's SCORM calls show in the browser's console, which tells your Docebo admin whether the finish call arrives. Alder's Docebo profile is built from those two Docebo articles and hasn't been tested on a real Docebo yet.

Alder's Docebo notes cover SCORM packages. If your Rise course is published as xAPI, they don't apply; there is a Docebo community thread on Rise xAPI courses not always being marked complete.

Why it happens

Docebo's help centre says the platform identifies SCORM content as completed when learners press the Close button, also named Exit or Submit (Uploading and managing SCORM as training material). Its debugging article tells learners not to close the course's window with the X button, and to look for a Submit or Close button first (Using the SCORM debugging option). That button normally ends the course's session with the LMS (in SCORM terms, it calls LMSFinish or Terminate). When the window closes first, the course may never get the chance, so it works for learners who use the button and not for those who don't. Some courses end on a “thank you” screen with nothing to press, so every learner closes the window.

Still not working?

• Start with the general checklist: works in SCORM Cloud but not in your LMS.
• Learners lose their place on long courses: see the suspend_data limit.