Forum Discussion
Learner navigation is stopped, next button doesn't work until resetting course
I'm working on a course of 10 modules for a client, and due to some very strict restrictions from them, I created the triggers shown in the image on the default Storyline Next buttons. I export the modules as SCORM files to place in their Canvas LMS. The Storyline files are split up into scenes, each of which I upload as an individual SCORM file.
We have found that, in each of the modules, at random times, with 0 ability to replicate or expect, and generally at least once every 100 or so slides, the next button does not move the user to the next slide. It can be clicked, but it won't advance the slide.
Here are some facts to help illustrate the situation further:
1. I have a Jump to Next Slide trigger on every question slide with two conditions to meet before the next button works: Get the question correct OR attempt it 2 times. Each question has 2 possible attempts allowed. There are around 110 slides on each module, and 80% of the slides are question slides.
2. I have set the navigation to restricted, but with the "restrict next/back buttons" toggle turned off.
3. This issue only occurs on slides with the triggers shown in point 1.
4. I am yet to have this issue occur on the same slide in my testing. But it has happened on a wide number of question slides, no matter the variety.
5. It happens in preview mode, review 360, and in the Canvas SCORM player. More often than not, the issue occurs while the module is in Canvas, but I have had it happen outside that environment.
6. The client asked that, even if they get the question wrong, that they continue through the learning.
7. Once they learner encounters this bug, they have to restart progress in the course to get through. Refreshing the page doesn't solve the issue.
I've attached the entire .story file that is a common culprit, and I've also linked to the first scene of it in SCORM cloud for testing. I can attach a .zipped SCORM version of the first scene as well, in case anyone is interested in testing stuff. Here is step 1 and step 2 in Review 360.
I can't guarantee you will find the bug in your testing, but if it does happen, yippee!
While I would be happy to learn of why this issue is happening, and how to solve it, I would also be happy to hear of any alternatives to entirely dodge the problem. It would be very difficult to convince the client to accept custom buttons for navigation, so that's a limitation unless it is my only way out of this.
Thank you all for the help!
2 Replies
As the next button is always active, it is likely the condition is not firing correctly.
I would have disabled the next button and then enabled it off of those variable values.
When you have been able to replicate it have you checked the variable values in the console or added in a references to check?
Sounds like you can replicate it, my first stop would be to add references and check the values when the error occurs.
For me it would have been easier to disable next on slide load and control the enable based of the correct or incorrect layer showing.Thanks for the reply Phil! I made the following trigger changes and I think it is working more effectively.
Though a client gave the following feedback upon testing it. Could be a fluke, but waiting on more feedback.
"I got stuck here. Was able to move on by submitting repeatedly. But Next button stays gray and if I navigate back to this slide (using the menu or Previous) I cannot advance using Next."
I could also adjust the trigger to work when the users click "continue" to close the feedback slide layer, perhaps.
Any thoughts?
