Forum Discussion
Unexpected "Yes/No" Prompt in SCORM Output from Storyline 360
Hi, I was curious if there's any updates on this topic, as we are experiencing the same thing when updating older Storyline courses (e.g. created between 2022 till 2025).
For our updates, we replace the current course ZIP-file in our LMS (Totara) with a fresh ZIP-export of the course created in the current version of Storyline, and then save the course. This never created problems until earlier this year.
Now, if a user previously started the course before the update, and relaunches the course after the update, they get a screen with green buttons and a Yes/No prompt. I added a screenshot of this. This is after they got the normal Resume / Restart prompt and clicked Resume. The Yes/No prompt does not work. The first 3 slides of our restricted navigation go back to locked. Depending on a persons progress, further slides might be unlocked. New course users do not experience course problems so the problem seems to be with resuming.
Right now I'm holding off on course updates, as both of my recently updated courses experience the same problem. However, course updating can not be avoided forever. I would like to solve the problem before updating more courses.
Thanks in advance and if further information is needed please let me know.
Hi Femke_G,
Thanks for checking in on this.
Currently, this is the expected behavior after the file structure has been updated for LMS output. When learners who previously accessed an older version launch a newer version, issues can arise if the LMS retains the old suspend data. The updated course structure may no longer match what the suspend data is now referencing.
To avoid confusion moving forward, we suggest applying one of the following steps:
- Manually clearing leaners' resume data (if supported by your LMS), or
- Instruct learners to select Restart instead of Resume when prompted.
Let me know how it goes!
Hi Steven,
Thanks for getting back to me on this! With the options that I have in Totara and Articulate, I'm looking for the most efficient solution for my learners. Manually clearing leaners' resume data after an update sounds like the best fit for this. For this specific example, let's take a course I uploaded in 2022 and I now want to update it to a course created in Articulate version 100 and up (so with the new data structure).
I have a few options for the settings, including:
- In the Articulate Player: Resume -> On restart: (Prompt to resume / Always resume / Never resume)
- In Totara LMS: Attempts management -> Force new attempt. This has 3 options:
1) No - If a previous attempt is completed, passed or failed, the learner will be provided with the option to enter in review mode or start a new attempt.
2) When previous attempt completed, passed or failed - This relies on the SCORM package setting the status of 'completed', 'passed' or 'failed'.
3) Always - A new attempt will be generated with each re-entry and any previous attempts will be ignored.
I think these are all the options I have. What I want to avoid is learners always having to restart a course, removing the resume option, meaning they can't pause their learning and continue at a later point at all, especially for longer courses.
What I would be okay with is for the people who are mid course and haven't finished it yet, to reset their course progress once after I updated a course, but then after the update and restarting the refreshed course, they can just pause and resume as previously possible. So if their progress is deleted once, because the course was updated, that's fine with me, but I want to avoid forcing them to always restart, effectively completely removing their option to pause and resume in the future.
I don't want to remove course completion data from people who did complete the course before the update, I would just want this to affect the people who were mid course.
What would be the best way to set this up, given the options that I have with Articulate and Totara? Thanks in advance for working with me on getting this issue resolved!Hi Femke_G,
Thanks for following up and sharing those details. I'm happy to chime in!
What you’re describing aligns with behavior we’ve seen when older Storyline courses are updated and the LMS retains older suspend/resume data that no longer matches the updated course structure. That mismatch can lead to the unexpected Yes/No prompt and navigation issues after resuming.
Based on your setup, manually clearing resume data for learners who are mid-course would likely be the cleanest option, since it allows learners to restart once after the update while still preserving normal resume behavior moving forward.
I hope this helps clarify the best path forward for your setup.
