Forum Discussion
Unexpected "Yes/No" Prompt in SCORM Output from Storyline 360
No news on this? now when i want to revert to previous versions can't open due to rounded borders control... this has no sense
Hi DenisBonenfant & TMerrifield!
Thanks for reaching out about the issue you've had with resuming courses in your LMS!
I'd like to share some background information and a suggestion that I hope will fix the problem. Starting with Storyline 360 update 100, we improved how the data used for allowing courses to resume is stored. That also changed its data structure.
While many LMSs like SCORM Cloud automatically clear old resume data when a new course version is uploaded, other LMSs may retain that data. That can cause issues if a course was originally published before update 100 and later updated. The older resume data won't match the new data structure, which can lead to unexpected behavior when learners try to resume. To prevent that, we recommend asking learners to choose "Restart" instead of "Resume" when prompted. This gives them a fresh start with compatible data.
Please note that once incompatible resume data exists, it cannot be recovered. However, if all SCORM packages for the course were published using update 100 or later, you shouldn't encounter this issue moving forward. The Resume data stays consistent across those versions.Please let us know if you have any questions!
DenisBonenfant and StevenBenassi
Same, we rolled back to update 99. This worked for some modules, but others wouldn't open due to the rounded corners issue. Now if we have to make additional updates to these older modules, we'll have to roll back to update 99 again? This is really inconvenient. And the condescending automatic responses from Articulate Staff repeatedly telling us "we're in good hands with their colleagues" is frankly annoying.
StevenBenassi Hi Steven,
Thanks for sharing background information on this problem. We have unfortunately been dealing with this too when updating Storyline courses in our Totara LMS.
As for courses developed in Articulate Rise, has the way data is stored for course resuming and the data structure also been changed there? We recently have been having some trouble with an updated Rise course that we can't really explain, hence why I'm curious if it might have something to do with the data structure. Thanks in advance for letting me know!Hello Femke_G
I'm sorry to hear you've been experiencing this behavior with your Storyline courses in your LMS (Totara)! I appreciate your inquiry regarding the data structure in Rise 360. I've opened a support case on your behalf so our talented Support Engineers can take a closer look at this with you. They'll be in touch via email shortly. You're in excellent hands!
Hi Steven,
In regards to the background information you shared I have an additional question below, after some context.
This is mostly regarding your statement " Starting with Storyline 360 update 100, we improved how the data used for allowing courses to resume is stored. That also changed its data structure. [...] The older resume data won't match the new data structure, which can lead to unexpected behavior when learners try to resume."
I saw this today when wanting to publish a Rise course: "LMS exports are updated. If you have compatibility issues, temporarily switch to legacy export until August 7, 2026" When reading more information here: Rise 360: Using the LMS Package Legacy Exporter I saw this:
"To improve reliability and pave the way for future improvements, we’ve modernized the backend architecture for all LMS exports in Rise 360. [...] The latest update doesn't change how LMS Export packages perform for learners, but it does change the package's internal architecture. That may affect how your LMS handles the data. While we don't anticipate the update causing issues for most users, those who modify their exported package files and/or deploy to custom LMS systems may encounter compatibility issues."
My question is: Does this mean we can expect similar problems to what we had with Storyline courses due to changes in data structures, now with Rise as data structure will be changed there too?Hey Femke_G,
I completely understand your concern! While these two situations are somewhat related, they're not entirely the same.
With Storyline 360 update 100, the resume data format changed for all newly published courses. Which meant LMSs that retained older suspend data could run into compatibility issues when learners resumed an updated course.
With the recent Rise 360 LMS export update, the primary change is the internal architecture of the exported package. For most users, this won't affect learners or require any action. The temporary Legacy export option is available primarily for organizations whose LMS or deployment relies on the previous package structure.
There is one important consideration I'd like to highlight for those who switch between the new and Legacy exporters for the same course. Learners who have already completed the course won't notice a difference, but learners who are in progress will have their progress reset if you overwrite the package using the other export model. That's why we recommend enabling Reset progress after updates when switching between exporters.
While both Storyline and Rise involve changes related to resume data behind the scenes, we don't expect customers who continue using the default Rise exporter to encounter the resume compatibility hiccups that accompanied the Storyline update. The scenario to avoid is switching back and forth between the new and Legacy exporters for the same course while learners are actively in progress.
That said, if you and your team experience any issues with Rise's new default LMS option, please connect with us through a support case. Real-world examples help us improve reliability for Rise's default exporter.
