It sounds like Captivate is remembering where they left off and returning the reviewer to it. Captivate makes it a bit hard to override that setting. What might be easier is to reset (delete) the SCORM data which will remove the bookmarking/suspend data. This article will explain that: https://blog.reviewmyelearning.com/scorm-log-lets-peek-under-the-hood/
The Review Trap Most eLearning review cycles fail because they start at the wrong end of the priority list. Stakeholders get bogged down in comma placement and brand colors while the underlying instructional logic is fundamentally broken. When you reach the end of a project and realize a branching scenario
The Failure of the Post-Course Survey Most eLearning feedback dies in a post-course survey. We ask learners to recall their experience after the fact, resulting in vague comments like "the navigation was confusing" or "some parts were too slow." For a developer or L&D
eLearning courses act as living systems where maintenance costs frequently exceed original development costs. Learn why courses 'rot' and how to prevent technical debt.
As an Adobe Captivate developer using JavaScript, debugging your project often requires checking the browser console for messages, warnings, or errors. However, if you're working in a production environment or using specific JavaScript code, you might notice that console.log and other console functions appear to do nothing.