Storyline 3 - passing score, no completion in our LMS - HELP!

Aug 28, 2018

Hello Articulate World!

So - we use Storyline 3. We also use SumTotal LMS. For a reason I really cannot troubleshoot, I have a course that works perfectly in preview and on the web, but will not register a completion in our SumTotal LMS. I am also not a SumTotal expert. Our LMS Administrator (who is pretty much the expert) and I are working together to problem solve this mystery!

Quick Notes:

SCORM 1.2

HTML5 Only

Tracking: set to Results slides (all good, requires passing 80%)

Reporting/Tracking details to the LMS set to Passed/Incomplete

Has anyone ever experienced this or something similar? Any suggestions are appreciated!  Thanks in advance for sharing your thoughts! 

7 Replies
Leslie McKerchie

Hi Heather,

Thanks for sharing what you are seeing when you publish your course to SumTotal. 

Using a setting of Passed/Incomplete should allow both a completion and success status to be shared with your LMS.

Curious if you experience a similar issue if you upload your zipped published output to SCORM Cloud or is this issue limited to your LMS?

Katie Riggio

Hi there, Heather. Really sorry you're running into this tracking issue in SumTotal. oopsie I stepped on Leslie's toes here! :)

Here are the four pairs of values that can be reported to an LMS:

  • Passed/Incomplete
  • Passed/Failed
  • Completed/Incomplete
  • Completed/Failed

Does your LMS only track a completion status? If so, could you see if selecting either the Completed/Incomplete or Completed/Failed value instead helps to resolve the issue?

Additionally, Leslie raises a good point: Have you had a chance to test the course in SCORM Cloud? If it reports as expected there, it might be helpful to enable LMS Debug Mode to capture the communication flowing back and forth between your Storyline course and SumTotal, and share that data with your LMS admin.

Hope that helps, and we're here if you need a hand with testing!

Ashley Terwilliger-Pollard

Hi Wilson,

Our team has an account at SCORM Cloud that we can upload files larger than 100 MB too, so if you'd like us to test it out can you share a copy of your .story file with our Support Team

Did you also look into enabling LMS debug mode and review the ways in which completion and success are passed to an LMS? 

Lindsey Brockish

Hi all,

I'm have a similar problem with our Storyline 3 SCORM content in our Bridge LMS. The Bridge tech support team is also working to help me solve this. 

Our issue is that the attempt limit imposed by the LMS doesn't correspond with the SCORM attempt limit we built in for the knowledge check. SCORM seems to be passing information back to the LMS that an attempt has been made on the quiz, even if only a few or none of the quiz questions were answered. This only happens when 1 failed attempt has happened and the user has exited the course and then resumed (set to force resume).

I'm using SCORM 2004, 4th edition. I've tried all 4 completion/success passback combos without success: 

Passed/Incomplete
Passed/Failed
Completed/Incomplete
Completed/Failed

Our hypothesis is that the SCORM package is sending completion data that is 'leftover' from the first attempt when the second attempt is made. When that score data is sent from the quiz slide (not the results slide), the LMS registers that as an attempt. Instead I need the package to only pass back data from each unique submission of the results slide. 

Has anyone had the same issue, or better yet, found a solution??

Thanks in advance,

Lindsey

Alyssa Gomez

Hello Lindsey!

Storyline sends data to your LMS as the learner answers each quiz question, and then the final results slide will send the total quiz score. If you want to see how and when the data is being sent to your LMS, you could enable LMS debug mode

It would also be worth testing your course in another LMS environment, such as SCORM Cloud. That would allow you to compare the behavior from your LMS to an industry standard and use the information gathered to share with the Bridge LMS support team.

This discussion is closed. You can start a new discussion or contact Articulate Support.