Unexpected "Yes/No" Prompt in SCORM Output from Storyline 360

Thank you for continuing to investigate this issue and for the updates provided throughout this discussion.

My team is experiencing the same behavior within our Moodle LMS environment, and rolling back to Storyline version 99 is unfortunately not a practical option for our team. Similar to others who have commented, we support a large learner population, and manually clearing resume data for affected users would be extremely time-consuming and difficult to manage at scale.

In addition, instructing learners to select Restart instead of Resume is not a viable long-term workaround for us. Many of our courses are lengthy, contain significant amounts of required content, are gated, and are intentionally designed to allow learners to return to where they left off. To further complicate matters, our client has requested that learners maintain ongoing access to course content, making it difficult to implement solutions that require learners to restart courses or lose their saved progress.

Historically, our team has installed Storyline updates as they became available. However, this experience has made us more hesitant to adopt future updates immediately. While we understand that no software vendor can test every possible LMS configuration, the limited detail provided in Storyline release notes and the lack of visibility into which versions are considered stable make it challenging to assess risk before updating.

Could you provide additional insight into the testing and quality assurance process for Storyline releases? Specifically, does the engineering team perform regression testing against common LMS platforms and SCORM resume functionality prior to release? Additionally, are there recommendations for organizations that need to keep content current while minimizing the risk of negatively impacting learners who have existing course progress?

Based on the volume of responses in this discussion alone, it appears that this issue has affected a significant number of organizations and learners. Since course content must continually evolve and be updated, we are looking for guidance on how to confidently maintain and republish content without risking disruptions to the learner experience.

We appreciate the team's efforts to identify the root cause and look forward to any recommendations that can help us and other organizations manage course updates more safely moving forward.