Forum Discussion
Storyline 360 Quiz lockout after failed attempts(7-days cooldown)
Hi community,
I'm facing a significant challenge with my Articulate Storyline 360 project settings, and I'm hoping someone may have found a working solution for a similar scenario. I've already spent several days troubleshooting this issue, including working with Claude Pro, but I haven't been able to fully resolve it.
I have the following requirements from stakeholders for a 30-question quiz in Storyline 360:
1. The quiz should allow 2 attempts. The next 2 attempts qill be allowed aftr 7 days if the previous 2 were failed.
2. The passing score must be 100%.
3. If the learner fails the second attempt, the quiz should be locked for 7 days. Even if the learner closes and reopens the SCORM, it should still display that the quiz is locked and indicate when it will become available again.
4. Each time the learner opens the SCORM package, it should display how many days remain until the quiz is unlocked.
5. After the 7-day lock period expires, the learner should receive 2 additional attempts.
6. If those additional 2 attempts are also unsuccessful, the quiz should be locked permanently.
I have attached the story file with 3 testing questions.
I have managed to configure variables that lock the quiz after the second failed attempt. However, when I reopen the course, Storyline does not display the correct layer, and the learner is still able to click "Retry Quiz."
Our LMS does not provide functionality to support these requirements at the platform level, so the entire solution needs to be handled within Storyline and SCORM persistence.
I would greatly appreciate any advice, examples, or recommendations from anyone who has successfully implemented a similar solution.
1 Reply
- jimmyadneCommunity Member
This is a really interesting use case. The biggest challenge seems to be persisting the lock state and countdown across sessions rather than the quiz logic itself. I'm curious whether anyone has successfully implemented a time-based lockout entirely within Storyline using SCORM suspend data. Handling the 7-day cooldown, restoring the correct layer on launch, and enforcing a permanent lock after additional failed attempts sounds like a good test of Storyline's persistence capabilities.