Same course, same question, different results?

Hi all,

I have a course loaded on SuccessFactors which was delivered to thousands of employees this morning. It was thoroughly tested before deployment from within the LMS and in Chrome and IE. The activity has two drop targets, and some drop objects appearing one at a time. It is allowing two attempts, per drop item, first incorrect shows try again feedback, then they get correct/incorrect feedback.

The problem we are having is that we have a few people who receive the try again layer regardless of which drop target they are dropping the first drop object on. I've observed what they are doing, and they are dropping completely inside the correct drop target.  We have 140 successful completions a few hours after assigning it to everyone, so are quite baffled why these four people are getting a different behaviour..

Any thoughts? Things we might be able to check?

2 Replies
Nicole Legault

Hi there Stacy, 

Sorry you've encountered this frustration! Sounds like this could be an issue related to your LMS. In order to find out if this a Storyline problem or an LMS problem, you can follow the instructions in this article (Troubleshooting LMS Issues) for uploading content to SCORM Cloud. 

SCORM Cloud is an industry-standard testing engine. If your content works properly at SCORM Cloud but not in your LMS, open a support case with your LMS provider to troubleshoot the issue. Your LMS provider may request a debug log to help identify the problem. Click here to learn how to generate a debug log.

If your course doesn’t play correctly at SCORM Cloud either, submit your project file to us for review.

Hope this helps! 

Stacey La Hack

For anyone who experiences this in future, check the IE version of the people having a problem.  Because they were so geographically spread out it took time for people to come back with screenshots of their IE version. We found the problem was with people who had IE 11.0.9600.19035. For some system reason, yesterday Chrome was reproducing the issue in those people, but a PC restart and we have the same issue in IE but not in Chrome.