Forum Discussion
Course resets after completion despite resume settings in Player
Hi, my team is facing an issue in which all our courses, after being completed by students, completely reset.
Our courses all have Restricted menu navigation so that users may not jump ahead, but may return to slides they've already visited.
We have tried both "Always resume" or "Prompt to resume" on restart in the Player settings.
Experiencing the following behaviors:
- GOOD: If a user is part way through a course, exits it, then returns, the course successfully resumes where the user left off.
- PROBLEM: If a user completes a course (passed, marked as complete in LMS), exits it, then returns, the course resets - meaning the user is dropped on the first slide of the course rather than last, the menu becomes fully restricted as if the user was just beginning the course for the first time, and all slides set to Resume Previous State must be watched all the way through again. This is preventing use of completed courses for reference material.
How do we get completed courses to save their menus' fully "unlocked" states?
(Note: We are using Storyline 2.)
Hi, I found this thread while researching about an issue we've just encountered. In our case, the user hasn't even successfully passed the quiz. After exiting the course on the Result slide of their failed attempt, resuming the course would already bring them back to the first slide of the course. They are supposedly allowed to retry the quiz with an unlimited number of attempts.
I am having the same issue. I have created 10 other courses and this does not happen. Its only happening to 3 and i cant figure out why. i built them the same exact way.
Hi tabsanss!
Sorry to hear the resume settings from your course aren't working as expected!
Are you experiencing this behavior after publishing your course to LMS? If so, have you had a chance to test the SCORM package with SCORM Cloud? If the same behavior can be observed in an LMS test environment, it would be helpful to see one of the files that's giving you trouble. Feel free to upload a copy here, or privately through a support case.
Looking forward to hearing from you!
Hi Nicole,
I see you posted a similar question in the Cornerstone conversation here.
Were you able to find the setting that was referenced by Matthew or is this an issue that you are able to replicate in SCORM Cloud and you would like us to take a look?
Hi Leslie,
These two are actually different issues. I replied to this thread because the latest issue I encountered is similar to this one. The problem I posted about in the Cornerstone thread is related to a user getting stuck on a random page.
In this case, the user is able to get to the end but even if they have unlimited attempts to retake the final quiz we've set up and they've failed it, exiting the course while on the Result slide refreshes the course and brings them to the beginning once the decide to resume. It doesn't give the user an option to either resume or restart the course.
Thanks for those details, Nicole. That behavior might make sense if learners passed the assessment, but I would expect them to return to the results slide with the option to resume after failing and exiting.
With your permission, I'd like to take a look at your .story file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting!
Thanks for the additional testing and information, Amy.
I appreciate you reaching out to the support team. I can see that Richard is taking a look and you should be hearing from him soon.
Hello,
Are there any news about this issue?
Would be very interested as I face the same issue (after completing getting back to the very start).
Hi Marcel,
Sorry to hear you're facing the same issue! Have you tried testing this behavior in SCORM Cloud? Checking your output in another LMS environment will help sort whether this is LMS related.
If this is urgent, feel free to reach out to one of our support engineers, and they can help troubleshoot and find a workaround if possible!
Thank you Ren,
I tested in Scrom Cloud. I face the exakt same issue there as well. I already applied the changes in Configuration.js (var REVIEW_MODE_IS_READ_ONLY = false;)
Further more, when I passed a certain slide in the training and close the window, I get back to exactly that slide when I reopen it. It's a bit strange for me, as this is not happening in our LSM (avendoo).
Hi Marcel,
Thank you for the additional information. Good call on opening a Support Case! I see that Angelo is currently testing your file and will provide more updates when he is finished troubleshooting.
Please let us know if you have any questions!
Hi,
Is there any resolution on this ?
We have a Question bank of 20 questions (randomized), on the results Slide we are pushing a Complete/Passed status if the score is >90% and an Incomplete/Failure status if the score is <90%.
We also have a Resume saved state marked for all the slides, while bookmarking is working fine for all the pages, When we reach the Results slide and reopen the course from the LMS, the Course is re-opening from the 1st slide. We want it to open on the Results slide only. We have enabled the Player settings as Always resume. Please consider this as priority and provide a resolution at the earliest.
Due to company policy, we're not able to share the story file. Let me know if you would requrie anything else.
Hi Articulate staff,
Has there been any resolution to this issue? I'm encountering similar issues to the above folks.
Using SCORM 2004, 4th ed and Bridge LMS. Navigation is set to restricted (locked down on first attempt, free after completion). Prompt to resume is turned on. If the learner completes the course, closes it, and then relaunches it, they are prompted to resume or start from beginning (expected). However, if they opt to start from the beginning, the navigation is locked down again and they are forced to take the course over again.
This is unacceptable. Once the course has been completed and passed, any further access to the course should be in review mode only. The course should never reset the learner's status to incomplete and lock down the course again unless the LMS admin has manually reset their attempts in the LMS itself.
I have confirmed that the issue is occurring in SCORM Cloud. See attached screenshot -- completion status was reset to incomplete and navigation was locked down again after I launched the completed course and opted to restart from the beginning. As it is now, I will never be able to use prompt to resume if I also have navigation set to restricted for first pass, and the alternative (always resume) is not good when our internal learners need to review changes in an updated course but not be forced to sit through the entire thing.
I see above that blame is often cast at the LMS, but I do not believe Bridge is the culprit in this instance. Their documentation specifically states that once a learner has completed and passed a course, it's a done deal: Any further data sent to them by the SCORM is essentially 'ignored' by the LMS unless the admin resets the learner's attempts.
I know that there is discussion above about manually tinkering with the configuration.js file, and in my opinion, this is unacceptable. We should not have to tinker with Articulate's output files to work around poor functionality.
I'd like to see Articulate expand the options related to navigation lockdown and course restart to allow us to specify what means to restart a course from the beginning (i.e., resetting course status vs. jumping to the beginning in review mode).
I appreciate any update that Articulate staff can provide, and I'm happy to create a feature request if that will help.
Thanks,
Lisa
In my case, the issue came itself from the LMS I was using.
I just had to fill one empty fields with a translation from German to English in the prepared course.
Afterward, miraculously everything worked as it should have done before.Totally agree with you, I am facing a similar issue, I can get the Custom Menu to unlock on Review mode by setting and calling a variable, my problem is on the second attempt (Redo Mode) everything gets reset just as the first attempt.
Hello Salvador!
Our team is happy to help! Do you mind sharing your project with us so we can see what you've created so far? Here's a secure upload link. We'll reply after reviewing the project. Lastly, we'll delete the file after troubleshooting.
I too am having the same issue. Storyline 360, Using TinCanAPI publishing to LMS. Course shows passed, based on a quiz results slide, but when user re-enter the course, even though player is set to resume saved state, course starts completely over. We want the first time use to be with restricted navigation but subsequent uses to be as reference so do not want it locked down.
Yikes! Looks like I just missed you when replying, Laurie!
We'd love to lend a hand if you can share your course with us. We delete all files after troubleshooting!
Greetings, Lisa and SIM!
Thanks for taking the time to write up that helpful description. We'd love to help you both find the culprit, especially since the problem is happening SCORM Cloud!
You mention that any further access should be in review mode when learners complete and pass the course. Could a 'Review Quiz' button work for your design? That way, learners can go back to review the answers they submitted without changing their answers or retaking the quiz.
Also, would it be possible for each of you to share your file to help us illustrate this experience? If that works, please use this secure upload link.
I'm sorry for the trouble, but hopefully we can offer some tailored help!
Hi Katie, mine are either standalone software demos with no quizzes, or courses with quizzes in separate SCORM outputs. There are no quizzes embedded in my courses (an LMS fix... long story...). This is occurring even in outputs where there are no quizzes. In those cases, completion is marked with either a course completion trigger on the last slide or by the number of slides viewed.
Thanks,
Lisa
Hello,
I have been in contact with a support person who is not able to resolve the issue and he's been at it all day. Sounds like it's a bug.
