Activity is working fine in preview, but not in published version

I have an activity built that shows the correct feedback in the preview, however in the published version that I tested in my LMS, the feedback says "incorrect", but lets me move on like the question was correct.  If I get it incorrect in the preview mode, I cannot move forward until it's correct.  I'm using SL 360.

Any ideas?

Best,
Julie

6 Replies
Julie Stout-Matthews

Hi Wendy,

I think I MIGHT know what's causing it, but I don't know how to fix it. I had this situation before, when I first switched to SL360. My files would automatically publish to HTML5/FLASH. This was causing my LMS to recognize modules complete before the course (which had 9 modules) was complete. I was told by technical support that it was a known issue with SL360 that was being addressed. They told me to manually set the publish format to Flash/HTML5 so I did and it fixed the issue.  It hasn't happened again up until this situation.

Last week I published this module by itself and tested it in my LMS, not realizing that it reverted back to publishing in HTML5/FLASH. It worked perfectly.  I uploaded the rest of the modules, which again, I didn't realize published to HTML5/FLASH and I couldn't get past one module without it triggering the course to complete.  I went back through old tech tickets and checked and sure enough all of the modules were publishing with HTML5/FLASH. I republished them and changed the setting for all of them to Flash/HTML5.  When I retested the course again, I was able to successfully complete ALL of the modules, however, I ran into the issue mentioned in my original post.

Do you think this could be causing the issue? 

I'm attaching the story file for the unit if you want to take a look.

Thanks so much for your reply.

Julie

Alyssa Gomez

Hi Julie! I want to make sure I'm understanding the issue correctly. Did you publish for LMS and use the Flash/HTML5 format? And if so, can you please tell me which slide gives you incorrect feedback but allows you to move forward? 

Also, is this an issue that you are able to reproduce when testing in SCORM Cloud? This will help determine if the issue lies within your LMS or the actual project file. If you are seeing the same thing in SCORM Cloud as you're seeing in your LMS, let me know, and we'll troubleshoot further!