Retry only incorrect questions with branching not working?

Hi all, 

I created branching questions to test out the new feature - only score viewed questions.

On the result slide, I set up a retry quiz button to go back to incorrect questions and it did go back to the questions I answered wrong. However, on the last incorrect question slide, nothing happen after I clicked Submit button (as it should go back to the result slide?). 

Are there other triggers/variables I need to set up manually to achieve what I am trying to do? 

I have attached the story file. 

Thank you for your help! 

6 Replies
Carrie W

I think I found the issue. The "only score viewed questions" feature is not compatible with "retry only incorrect questions".

Say that I have 15 questions (for branching purpose) but users will only see 4 questions in total based on the answers they provided.  In Quiz Settings, I checked all the questions I wanted to include. 



The "retry only incorrect questions" still brings me back to the questions I answered wrong, but it won't proceed to the result slide after I re-try those incorrect questions. 

If I only check the question slides that I actually visit in Quiz Settings, the retry only incorrect questions will work properly. But this remove the purpose of branching and only score viewed questions. 

Is there any reason that these two features - retry only incorrect questions only and Only score viewed questions - are not compatible? The only reason I could think of is that branching quiz is customized and which questions you see the next is based on what you answered previously.  So retry only incorrect questions doesn't have much purpose here?  


Lauren Connelly

Hello Carrie!

I'm happy to help! It looks like you're on the right track. I noticed that might be happening since the Feedback Layers have the trigger to Hide Layer above the Jump to Next Slide trigger. I'd recommend removing the Hide Layer trigger.

Secondly, I moved the questions into question bank and chose to randomly select one question from each question bank. I've also removed the Hide Layer trigger from the Feedback Layers. Take a look at the setup and see if this will be a simpler way to track how the learner will move through the course!

Carrie W

Hi Lauren. Thank you for looking into my file. However, What I wanted to achieve was slightly different than your example. I would like the "next" question to be specific based on what I answered previously, instead of random draw from question banks. See screenshot below - If Q1 is correct, it will branch to Q2A, and if Q2A is incorrect, it will branch to Q3A2, and so on.

So technically there are 15 questions but users will only see 4. 

I set this up to test out the new Score Only Viewed Questions feature that was rolled out on September 29 (see Allison's post here - 4. Create a Quiz That Adapts Based on the Learner’s Responses). The score was recorded correctly but the retry only incorrect didn't seem to work properly (I can see the flaws in using retry only incorrect on adaptive quizzes though.)

Any thoughts on this? Thank you. 


Ren Gomez

Hi Carrie,

Thanks for taking the time to troubleshoot this issue. It looks like you're running into the same bug that was recently reported with Haylee where:

A quiz will get stuck when retrying incorrect questions only, and the option to "score only viewed questions" is checked.

I'm sorry if this is slowing you down! I'll be sure to add your example to our report and jump back in here when any progress has been made.

Leslie McKerchie

Hi Carrie and Haylee,

Great news!  We just released another update for Articulate 360 and included a few important fixes you'll see in the release notes.

The item you'll be interested in is:

Fixed: When setting a result slide to score only viewed questions and retry only incorrect questions, the final score could be over 100%, or the result slide might not load.

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.