Forum Discussion
Recent update to Storyline breaks LMS resume
I have recently encountered an issue when I republish a Storyline SCORM Package, then overwrite it in an LMS, any users that were already in progress are prevented from resuming. I believe this issue has been introduced with a recent update. I have tried rolling back the version, but this doesn't help. I suspect the Articulate installer is not rolling back the cause of this issue (ie there might be some persistent system/profile files that contain the issue that are not getting rolled back). I have a version of Storyline on another computer that is only a few months older which does not exhibit this issue. My colleague has been able to replicate this issue with different Storyline courses. This issue is currently preventing us from using the latest/current version to update existing LMS deployed SCORM Packages built in Storyline.
I have been in contact with Articulate Support, but have had no luck so far. I'm interested to see if anyone else has experienced this issue or is able to replicate it. I have attached files to replicate the issue. Here are the steps:
- In SCORM Cloud upload a new course using test_course_sc2004-3_v1.zip
- Launch the course
- Close the course
- Notice in SCORM Cloud the course status should be marked as complete:
- Scroll down in SCORM Cloud and replace the SCORM Package by selecting Overwrite Course files:
- Overwrite the SCORM Package with test_course_sc2004-3_v2.zip
- Notice the course status should be the same as in step 4. If it has reset, it is because the SCORM Package was uploaded as a new version or the SCORM Package contained a different imsmanifest.xml file. Please confirm that you are still seeing that course is complete at this step.
- Launch the course again:
- Click the resume button:
- You should then see this screen (note this screen does not appear in the Storyline source file):
- Notice that the Yes and No buttons don’t do anything, so you can’t proceed.
- Close the course
SCORM status has now changed to incomplete:
I first noticed this issue using Docebo LMS with a different Storyline file, so I tested it in SCORM Cloud with a newly created Storyline file to verify it was not the LMS or the particular Storyline file that is causing the issue. The above steps for testing in SCORM Cloud are the same steps I communicated to Articulate Support. SCORM Cloud resets user progress if it detects that the imsmanifest.xml file is different when overwriting the SCORM Package, so I made sure the imsmanifest file in the replacement SCORM Package was identical to the original SCORM Package. If you are testing in a fully functioning LMS such as Docebo or Moodle, you won't need to worry about making sure the imsmanifest.xml file is identical - those LMSs won't reset user progress when updating a SCORM Package by default. So if you are performing this test in an LMS (ie not SCORM Cloud) you could republish the attached storyline file I have created as your version 2. Note that I published my version 1 SCORM Package from a version of Storyline that was last updated in May 2025, and the version 2 SCORM Package from a version of Storyline with the most recent update (November 2025). I'm interested to hear what test results people have and what version they are running - and then if they can replicate this issue with their own existing storyline courses.
I realise this is a complicated issue to reproduce, so please ask me questions if anything needs more detail.
Thanks,
Ben
11 Replies
Looks like the SCORM Packages didn't upload - trying to attach them one at a time here
Looks like zip files can't be attached, so here is a link to download them: https://drive.google.com/drive/folders/10p6zwBj9Q6hEJZR8LDKCR2HRj1Xe37Qp?usp=sharing
I tested this out with the files Ben provided and came across the same issue in the Cornerstone LMS. I loaded the version 1 file and completed the course. Then, I did an overwrite with version 2 and resumed the course which then showed the "yes" and "no" buttons that did not function. Exiting the course kept my completion status, however.
We’ve also been experiencing this exact issue with Storyline and HR Learn LMS. We made some content updates to three modules, and when we swapped the SCORM packages in the LMS course with the updated packages that were published after Storyline update 100, we’re getting the same prompt to resume screen with inoperable Yes and No buttons. Our modules are all set to “Always Resume” so this prompt should NOT be happening. We then tested a fourth module that was authored by different Instructional Designer, in a separate course and got the same Resume Prompt. This tells us that the original three modules developed by one ID were not corrupted files and that this is a global Articulate or LMS issue.
We’ve submitted two tickets to Articulate, their response:
“Starting with Storyline 360 Update 100, we improved how resume data is stored in our courses. As part of this change, the resume data structure was updated. While many LMSs (like SCORM Cloud) automatically clear older resume data when a new course version is uploaded, some platforms—such as your LMS—may retain the older data.
This can cause problems when a learner tries to resume an updated course. Since the old resume data no longer matches the new structure, it may lead to errors or unexpected behavior when the course loads.
We recommend asking learners to choose “Restart” instead of “Resume” when prompted to avoid issues. This ensures they start fresh with compatible data.
Just a quick note: the resume data is considered corrupted or incompatible when transitioning between pre- and post-Update 100 versions of the same course. Unfortunately, this is a permanent state—it can't be recovered once the data is incompatible.
On the other hand, if all SCORM packages for the course were published using Update 100 or later, you shouldn’t encounter this issue, as the resume data structure remains consistent across those versions.”We work for a large global manufacturer, with 85,000 users in our LMS and our content regularly requires updates. We need this fixed!
Hi TMerrifield!
Sorry to hear you've also been experiencing this issue!
I noticed that you're working with my teammate Robert through a support case. It looks like he replied to your e-mail sharing insight and suggestions.
If you have any follow-up questions, feel free to reconnect with him through your case!
Hi KennyDyer-44519,
It looks like my colleague, Steven, already replied to your post!
Let us know if you have any more questions!
Great 1st post Ben! - You did a great job documenting this issue that we have also been experiencing over the past 10 days. We have run over 20 tests trying to figure out a way to maintain our learner's current experience and manage our content administration. We also use Hire Road LMS. I have over 7 years admin working in Cornerstone - sadly, was a bit relieved that this did impact both Docebo and CSOD.
In Hire Road, we have the ability to maintain module data when we do a content swap. Here is the language: "Do not reset module data for learners on content change." We do select this when we swap out Zip file modules.Here is a graphic I'm using to communicate this to our management team as I explain the past week of testing. The purple highlights in the top table is what has changed for us. Before Update 100 the top table section would all be green, meaning the learner was not affected regardless of their module status.
Hi DaveDraper-c3de!
Thanks for reaching out!
I see that you and your team have been troubleshooting with my colleague, Lianne. Smart move! We can continue the conversation there to keep all information in one spot!
Hi BenButler-5d04c!
So sorry to hear you've run into these setbacks when uploading Storyline content to your LMS!
I see that your support case has just been escalated to my colleague, Clara. You're in excellent hands troubleshooting with her, and we can continue the conversation through your case!
Thanks to everyone that have confirmed this issue. I have also now received the Articulate Support response regarding the Storyline 360 Update 100. Essentially this update has changed the way resume data (suspend data) is saved, so older versions don't match up with newer versions. Ideally, I think it would be best if Articulate developers fix this issue in a future release. I understand that they need to keep the new method of storing data, and that it is not compatible with older versions, but they could at least resolve the JavaScript issue that freezes the SCORM Package. Rather than asking LMS administrators and users to address the issue when it arises. It would be much better for Storyline to catch the JavaScript issue as it occurs and present the user with a notification saying their progress will be reset - and then reset their progress via JavaScript.
In the meantime, I can think of a couple of workaround solutions:
- For me the best solution is to find an old version of Storyline that predates this issue. Note that rolling back doesn't seem to work, so you need to use an old version on a computer that has never updated to an "Update 100" version. I suspect the rollback method is not deleting or overwriting something and that it might be possible to replace/delete system files to do a proper rollback. I might end up comparing my old working version with the new version to see if I can figure it out. If I do, I'll post the solution. But if anyone else is good at figuring that stuff out, please jump in.
- Another solution could be to create new course versions in your LMS. Essentially this issue is treating these re-published SCORM Packages as different/new courses, so you could also think of them that way. So, leave all your existing enrolments in your old version course and create a new version of the course using the newly re-published version. Then all new enrolments will go to the new course. This may create lots of extra ongoing work for reporting etc because there will be 2 courses that may need to be stitched into a single report.
- Seems like the Articulate solution is just to reset everyone's progress. But I guess you could manage the communication and timing of this to minimise inconvenience, rather than waiting for users to report the issue and addressing it as it occurs. Eg - tell everyone in progress to complete their course by a certain date and if they don't their progress will be reset - then apply your update on that date.
I just tried using this method to delete user data: Articulate 360: Script to Remove Local User Data for Articulate 360 Apps on a Windows PC
but unfortunately, the issue persisted. I think the issue is in the system files, because I can see the text for the screen where it freezes - "Would you like to resume where you left off?" is in the Storyline system application file Players\KnownPlayerStrings.xml line 45. My older version on another computer that doesn't have this issue doesn't contain that text in the same file - that file has many differences. I don't think I'll be able to figure out which system files to change - it's a bit too unpredictable.
