Yes. There have been several causes we've identified, including (in no particular order):
- Module length (it seems that in some instances, exceeding 30 minutes could result in crazy behavior)
- Story file size ("size matters")
- Story title filename length (too long)
- Publishing to SCORM 2004 (though we've seen it also in SCORM 1.2)
- Using an "exit" course button that was added to the player (this was a big "find," so now we use that button judiciously, and are not seeing the problem at all when we simply "advance to next slide" and end the course automatically)
- Users not clearing a browser cache (we're strongly considering adding an "information" page in SF that advises employees to do this before launching a course)
- Reused artifacts within the story file (in one case, the developer had reused some variables from a different story that for some reason caused SuccessFactors to go all wonky)
Not an exhaustive list, but a few things to explore as you continue troubleshooting. My guess (based on your description) is that there is either some artifact in the SL file (see last bullet) or users are not clearing their browser caches (next to last bullet).
Good luck!
