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:

1. In SCORM Cloud upload a new course using test_course_sc2004-3_v1.zip
2. Launch the course
3. Close the course
4. Notice in SCORM Cloud the course status should be marked as complete:
   
5. Scroll down in SCORM Cloud and replace the SCORM Package by selecting Overwrite Course files:
   
6. Overwrite the SCORM Package with test_course_sc2004-3_v2.zip
7. 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.
8. Launch the course again:
   
9. Click the resume button:
   
10. You should then see this screen (note this screen does not appear in the Storyline source file):
    
11. Notice that the Yes and No buttons don’t do anything, so you can’t proceed.
12. 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