Intermittent disappearing button

Jun 01, 2023

Hello there! 

If possible, I would greatly appreciate your assistance.

In a completed module, uploaded to the LMS, some of the learners (2 out of ~400 completions) have come across a problem where a buttons disappears, meaning they are unable to continue the module.

The issue seems to resolve itself if I reset the 'started' status and allow the learner to start from scratch, but it would be good to know if there is a better solution to prevent the issue for everyone.

If it helps, the slide has 3 buttons, where each button take you through some slides and returns you back to this point. Experience all 3 areas and a new  button appears allowing the learner to continue. In both cases it's the same middle button that disappears.

I have hover & visited status' on the 3 buttons, built with triggers, not using the built in states. I also built the left button first, then duplicated it for the other 2 buttons, so everything is identical (except where the button takes you).

I appreciate 2 out of 400 isn't all that bad, but I'd rather it didn't happen at all, for this module and future modules where I may use this method.

Thanks,

3 Replies
Judy Nollet

Best guess: You say you have "hover & visited" states built with triggers. Are those states called "Hover" and "Visited"? If so, your triggers could be messing up the programming associated with those states. If you don't want to take advantage of the built-in functionality of standard states, you should use unique names. 

If your states do have other names, well, then I suggest you upload a copy of the .story file for troubleshooting. (Ideally, the uploaded file should only include the slides involved in the issue. If there's proprietary content, replace it with ipsum lorem or other bogus text.) 

Chris Dooher

Thanks for the response.

Your first point is a fair thought, but I had named the states differently (...well, not very differently) as "Hover1" and "Visited1".

I don't believe it's an issue with the slides/triggers as it's such an uncommon issue. If it was an issue on the slide then I expect I would see it more often, but I'll take your latter advice and clean up the .story file to submit. 

Thanks,