Spinning wheel when reviewing quiz after click next button
Oct 23, 2019
Wonder if someone could help me? I created review layers so I could show correct answers for drag and drop questions when the learner reviews the quiz. I have one layer that gives the spinning wheel and I can not get to the next slide. I have deleted the layer and recreated it. It's not happening with other drag and drop reviews. Could you please take a look? Here is the attached video of what it is doing as well as a screen shots of the layer, base, and properties. It occurs both in preview and Articulate 360. Any helpful would be much appreciated. https://360.articulate.com/review/content/f1457464-585a-4ea2-8226-1f714f58af5c/review
7 Replies
Hi there, Celeste. Thank you for that recording–it's super helpful to see!
That behavior typically happens when there's a corrupt element in the slide. Do you run into the same issue when importing the slides into a new project file?
With your permission, I can take a thorough look at your .story file to test this theory and nail down the culprit. If that works for you, you can share it publicly here or send it to me privately by using this upload link.
I have uploaded using the private link - thank you
This post was removed by the author
Hi Celeste,
Thank you! Would you be able to share your case number with us here to follow along?
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
I am sorry but I do not have a case number
Celeste Bramlett
So sorry for the hiccup, Celeste!
I created case #02014414 and sent you an email with the next steps. Let me know if you run into any trouble. Looking forward to digging deeper!
What was the solution?
Hi, Caleb, and welcome to E-Learning Heroes! ✨
If you're experiencing a similar behavior to what Celeste described above, I would encourage you to create a support case so we can dig into your project file to find the culprit.
In Celeste's case, it was a corrupt element in one of her slides. Re-creating the specific slide fixed the problem.
Let me know if this works!