Bookmarking/ Resume

Hi, 

I am having some issues with the bookmarking/ resume. I have recently published a new course that works fine in testing however when deployed onto our LMS (Totara) the bookmark/ resume feature does not function, we are using Edge (88.0.705.68) inhouse and Chrome (88.0.4324.150).

I have tested offsite and the issue is still occurring with edge and Chrome.

Interestingly when testing on other browsers there is no issue. I have tested in Firefox (85.0.2),  and IE (19042.804) and the function works as expected. 

I have created a small course with four slides with basic shapes and published the course and I am still experiencing the same issue. I have tested in SCORMcloud and again the same issue.

I have tried both player types again the same issue.

Finally I rolled storyline back to a previous version to see if it was a corrupt install and again the same issue.

Any help would be appreciated.

 

DC

2 Replies
Ren Gomez

Hi David,

I appreciate the troubleshooting steps you've taken, including testing your file in SCORM Cloud

Since you're experiencing similar issues there, I'd like to have our team take a look at your course and provide some guidance. Please share your .story file with our team, and they'll get right on it!

In the meantime, consider reviewing some of the solutions shared in this article that cover overcoming suspend data limits!

Leah Hemeon

Hi David,

Ren has some great tips (they are the Storyline experts after all :)) I happen to have significant experience with Totara (Moodle base). What version of SCORM did you publish to?

If SCORM 1.2 then you're likely running into SCORM 1.2's limits on Suspend Data. SCORM 1.2 is the "best-supported" version of SCORM in Totara/Moodle. In an average-to-long Storyline course, in my experience, it's been very, very easy to exceed that suspend limit. This isn't limited to Totara or Moodle. It's with any LMS using a SCORM 1.2 package. As the article suggests, if SCORM 1.2 is the best option (and as far as I know, it still is for Moodle/Totara's SCORM activity) then the best you can do is split your course into smaller modules and load them to Moodle as separate activities of the overall course. We do this all the time instead of using SCORM 2004. Moodle's SCORM 2004 module has its own issues.

If you're using Totara, then you may be working with an official Moodle Partner. If so, encourage them to fund more SCORM development in Moodle's base code or help them make the switch to TinCan API.

Good luck!