Forum Discussion
Issues with Final Assessment Processing Scores
Hello there,
Was hoping someone may be able to help diagnose an issue I and my coworker are both coming across trying to test a course that has different layers based on final assessment scoring.
The requirements are as follows:
- 15 total questions pulled from a pool of 25 questions
- 85% = Passing Score
- If the learner scores an 85 but does not get a perfect score, they must first review the incorrect answers and receive the "Review" layer before seeing the "Success" layer.
- If they have a perfect score, they would see "Success" layer.
- If the learner scores under an 85%, they will see the "Try Again" layer.
- The learner has a total of 3 attempts to pass the assessment.
- If the learner cannot pass in the initial + following 2 attempts, the course locks and they see the "Failure" layer.
I've done something similar before with another course, as well as seen it done in a course I did not work on, however this time upon completion of the assessment, we will see an infinite loading screen. The base layer appears, but the result layers never appear and instead the page remains "dim" and a loading icon is present.
If I fail, the try again button at least shows up after some time, but it isn't clickable or actionable as triggered - for passing, nothing populates.
Attached are my layers and the triggers found on each + example of the screen that appears.
Any ideas or obvious issues or incorrect triggers? Should this fix in an LMS? Thanks.
Hi all, thanks for all your various feedback and troubleshooting advice. I determined it was a couple factors - one of which being that the previous quiz these conditions were used on's Pass/Score variables were present in the results slide display (you see your score and what would be passing, like the default layout in Storyline) - this seemingly caused the endless loading.
The conditions were redone from scratch + and I used the master as a base and instead used a blank and added the layers in the actual slide (not the master). The "Try Again", "Failure" layers work as intended!
Then, to get the "Review" layer to hide after pressing the "review" button, and show the "Success" layer following their review, I needed the trigger to the "ReviewFT" to be on the main layer and set to hide on timeline start.
5 Replies
Best guess: there's a mix-up with the scoring variables.
When you insert a new Results slide, Storyline automatically creates the necessary built-in scoring variables.
If you copy-and-paste, duplicate, or import a Results slide, the variables get messed up. That prevents the slide from loading.
Usually, this can be fixed by adjusting the triggers to use the appropriate reference (if it's already been created). Or sometimes you can just rename the quiz to match the references being used in the triggers.
Also, be sure that the “score” and “percent” references in the text boxes refer to the appropriate variables.
And, sometimes, you just have to start from scratch by inserting a brand new Results slide.
I wonder if your browser's console throws an error you can read during the loading loop?
I'm struggling a bit to decrypt your triggers in your screenshot. Your main contains two slightly different triggers that both show the Success Layer. Is the second one redundant?
If I had to guess just from looking at them, I'd guess the "Hide this Layer when the state of Review Button 1 is Visited" trigger is the culprit. I think your intention is to hide the layer when the Review button is selected, but is it possible the layer is being hidden and never shown again when you want it to?
I'm also confused as to how the Pass - Review layer can show the success slide when the timeline starts on the layer if ReviewFT is true. ReviewFT only becomes true when the learner clicks the Review button. Can you confirm ReviewFT is triggering to true? Or does its place on the trigger list mean the "Review Results" trigger is firing first, shuttling the learner somewhere else before the trigger that sets ReviewFT to true can even fire?
Very hard to tell from screenshots. If you all can share a .story file, this would be much easier to troubleshoot. Without that, it'll be a lot of playing telephone.
One thing I'd check is whether any trigger on the result slide is creating a loop or waiting on a condition that never becomes true. I've run into similar "dimmed screen + loading icon" issues when a layer trigger conflicts with the built-in quiz result processing.
I'd also try publishing a simplified version with just the Success and Failure layers to see if the issue is tied to the review logic. If that works, add the additional conditions back one at a time.
Since both you and your coworker are seeing the same behavior, it feels more like a trigger/configuration issue than an LMS issue, but testing the published course outside the LMS could help narrow it down.
Hopefully someone spots something in the trigger setup screenshots.
It sounds like the issue may be related to the result slide triggers or conflicting layer conditions rather than the LMS itself. I would double-check the trigger order, variables, and any custom JavaScript that might be affecting the results slide. Hopefully someone in the community can spot the specific trigger causing the loading screen. Good luck troubleshooting!
Hi all, thanks for all your various feedback and troubleshooting advice. I determined it was a couple factors - one of which being that the previous quiz these conditions were used on's Pass/Score variables were present in the results slide display (you see your score and what would be passing, like the default layout in Storyline) - this seemingly caused the endless loading.
The conditions were redone from scratch + and I used the master as a base and instead used a blank and added the layers in the actual slide (not the master). The "Try Again", "Failure" layers work as intended!
Then, to get the "Review" layer to hide after pressing the "review" button, and show the "Success" layer following their review, I needed the trigger to the "ReviewFT" to be on the main layer and set to hide on timeline start.
