Skip to main content
Question

Failed status not available and user failed notification


Forum|alt.badge.img+1

We have an Articulate Storyline 360 course published as SCORM 1.2, with the reporting option set to Passed/Failed and tracking based on the quiz result.

When a learner fails the embedded assessment, the SCORM package reports Failed in SCORM Cloud. However, in Docebo, the learner’s course status remains In Progress, and we cannot see a failed result.

Why is Docebo not reporting the result as Failed?

We need to identify failed assessment attempts in order to trigger an immediate email notification “User completed or failed a test in a course” to relevant Power Users User when the user fails the assessment on an invigilated course which requires a manual tracking reset.

3 replies

Moshe.Machlav
Helper III
Forum|alt.badge.img+2

Hi ​@ChristineW,

What you are running into comes down to two platform architecture rules in Docebo: how course enrollment statuses work, and what actually triggers the test notification event.

1. Why the status stays "In Progress" (and why the notification isn't firing)

  • No "Failed" Course Status: At the course level, Docebo only supports enrollment statuses such as Subscribed, In Progress, and Completed. When a SCORM 1.2 package sends cmi.core.lesson_status = failed, Docebo records the failed state and score at the training material level (which you can view under Course Management > Reports > User Statistics / Training Material Statistics), but because the learner has not met the course completion criteria, their overall course status remains In Progress.

  • The Notification Trigger Limitation: The notification event Learner completed or failed a test in a course (Course.LearnerCompletedOrFailedATestInACourse) only triggers for native Docebo Test training materials. Because SCORM packages act as a black box to the notification engine, an embedded Articulate Storyline quiz will never trigger that specific notification—even when it passes a failed status and score to the LMS.

2. Recommended Workarounds

Before looking at custom integrations or webhook workarounds, have you considered decoupling the final assessment from the Storyline file? It might get you there without any integration overhead.

Option A: Move the final assessment to a native Docebo Test (Simplest & Most Reliable)

When I've deployed invigilated or compliance-heavy courses for organizations with similar requirements, the pattern that holds up best is keeping the instructional content in Storyline (set to track by slides viewed) and building the final graded exam as a native Docebo Test training material set as the End Object Marker.

  • Immediate Notifications: Because it is a native Test object, the Learner completed or failed a test in a course notification will fire immediately to your Power Users/Instructors upon a failed submission.

  • Attempt Locking & Resetting: In the Test options (Set attempt options), you can set Maximum number of attempts to pass the test to 1. If a learner fails, they are locked out until a Power User or Instructor navigates to the Course Reports tab and clicks the X in the Reset column for that learner's test.

Option B: Keep the quiz in Storyline and use Scheduled Custom Reports or Docebo Connect

If the assessment must stay inside the Storyline SCORM package (for example, due to custom branching or simulations):

  • Scheduled Audit Report: You can create a Users - Training Materials custom report filtered by that SCORM object and In Progress status, displaying the Score and Last Access Date columns, and schedule it to email your Power Users daily. (Note: this is scheduled rather than real-time).

  • Real-Time Alert inside Storyline: You can change the Storyline reporting option to Completed/Incomplete—or add a trigger on the Storyline "Failure" result slide—to either execute a JavaScript/webhook call (to a Docebo Connect recipe) that emails the Power User in real time, or instruct the learner to request a reset.

For full details on how each notification event is triggered and how to reset material tracking, check the documentation here:

Hope this helps clarify what is happening behind the scenes!


Forum|alt.badge.img+1
  • Author
  • Contributor I
  • October 21, 2026

Thanks for your response Moshe, really great information, 😊 really appreciate this and makes complete sense.

Unfortunately, many courses we sell, require the learner to be automatically sent back to the start of the course if they fail the assessment a set number of times and the one Scorm course we want the invigilators to receive the failed email is provided by the Client themselves and so we can’t use the native Docebo test.

We just have the course set like you explained that if a learner fails, they’re locked out until a Power User or Instructor clicks the X in the Reset column for that learner's test.

What you’ve explained certainly clarifies what’s happening behind the scenes and gives me a clear idea on possibilities going forward.


Moshe.Machlav
Helper III
Forum|alt.badge.img+2

Glad that helped clarify things, ​@ChristineW !

Having the SCORM package provided directly by the client definitely changes the game since you can't touch the source file or pull the quiz out into a native test.

Just so I make sure I'm pointing you in the right direction—when you mention selling courses and hosting a client-provided SCORM, are you hosting their learners inside your own Docebo platform (like an Extended Enterprise / client branch setup where your client's invigilators act as Power Users), or are you looking for a solution that runs inside the client's own LMS?

Also, for the courses where learners need to be automatically sent back to the start after failing a set number of times, is that reset currently happening inside the Storyline file itself, or are you trying to automate that reset inside Docebo as well?

If this is all happening inside your Docebo platform, there are some really clean ways to automate both the failure alerts to the invigilators and the tracking resets in the background without ever touching the client's SCORM file—happy to share how that works once I know a bit more about your setup!