Steps to Reproduce a Completion Status / Score Recording Issue?

Jun 18, 2014

I know there are multiple threads on course completion status and score recording issues on this forum. Just for reference here are some of them:

While it is rare some of our learner's do occasionally report issues like this every once in a while. We have taken the typical steps for this like adding a special slide for completion, adding language about how/when it's safe to close the course window (which I personally find embarrassingly awkward/unnecessary) etc.  However we still, from time to time, get reports of the problem.
Rather than post another comment in one of the many links above I thought I'd take another approach and start a new thread with an objective of coming up with a way to reproduce or simulate the actual problem ... again, where the end-user's score or completion status fail to be saved to the LMS. 

So ... does anyone know or have ideas on what factors trigger scenarios like this? Is it end-user bandwidth/latency related? Spyware/Antivirus software related? LMS server latency? Honestly I find some of these things fairly unlikely suspects (client software especially) but since I have heard other people mention them in the past as possible culprits I'm considering all options on the table at this point. 

In any case please share whatever ideas or thoughts any of you have! Oh and to keep test variables somewhat controlled let's assume the following:

  • The LMS being used is the SCORM cloud.  
  • The course is made with Articulate Storyline

Maybe if we come up with working/consistent steps for reproducing this issue we can create a public Google doc or something as a reference for authors / testers.  

Thanks in advance for any help/suggestions!  

(If a thread like this already exists please refer me to the link.)

Be the first to reply

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