Tin Can resulting in two completion statements

Feb 19, 2019

I have just started using the Tin Can publishing option, however when my courses complete the Tin Can file fires two completion statements which causes my LMS to send two completion emails to the trainee.  I am using LearnUpon LMS, is there a way to stop the Tin Can file from sending two completion statements? 

13 Replies
Alyssa Gomez

Hi Scott, 

Have you had a chance to test your content in another LMS to see if two completion statements are sent? SCORM Cloud is a handy tool for this kind of testing since it's industry-standard and it's free!

If the same problem doesn't happen in SCORM Cloud, I would recommend reaching out to your LMS administrator as a next step. 

Our team would be happy to help you with this testing if you'd like a hand. Simply share the unpublished Storyline file with us by clicking here. We'll delete it when we're done troubleshooting. 

Scott Dimmock

I have tested using SCORM Cloud and the issue is that the Tin Can is sending two requests at the same time setting the enrolment to “Failed” or “Passed” when a learner exits the Tin Can.

You can see how the 'Failed' statement is generated twice as per the attached.  When using the file in my LMS this means two completion emails are sent to my users.  Please can you suggest a way to solve this.  

Leslie McKerchie

Thanks for the additional information and that image, Wes.

Based on our documentation here, we report two activity types for the verb 'Passed' - the "Course" and the "Objective".

If you view the raw statement data through the xAPI Statement Viewer in SCORM Cloud, then expand each line and scroll down to the bottom of each report, you should see that each one corresponds to a different activity type:

  • xAPI_1
  • xAPI_2

So, each "Passed" verb we report correspond to two different Activity types based on our implementation of xAPI.

I hope that helps clear up any confusion.

Lauren Connelly

Hello David!

Great question! It sounds like you're hoping to disable the raw statement data for either xAPI_1 or xAPI_2. We don't have a supported method to achieve this, but I'm sure we have TinCan experts in this community who could offer a solution!

Excited to see what others recommend!