Bookmarking Changes in Published SCORM 1.2 files

Hi Boyd, this is sounding like a suspend_data field issue to me, and it sounds likely that suspend_data is going over the 4096 limit, and therefore not bookmarking beyond slide 23.

Can you confirm that the settings are being maintained, for example the slide property to determine if the slide should Resume or Reset. This is usually the biggest culprit. If several slides are set to Resume, the data for data persistence goes into suspend_data and you can quickly run out. If not essential to resume a saved state of a slide, set to Reset to initial state.

I'm unsure why this would be so different from a 2016 file, as I've thought it was always a problem, unless your LMS allows more than 4096 characters, and Storyline is actively truncating suspend_data values over 4096 characters in later versions, and not leaving it to the LMS. I'm pretty sure Storyline has handled the truncating for a good while though.

Would recommend a test of both files on SCORM Cloud to see what happens with the 2016 file on there and see if it does exceed 4096 chars.

I'm having the same issue. Publishing a SCORM 1.2 using the January 2020 version of Storyline 360 (version 3.36.21289.0) my projects bookmarking works fine.

Upgrading Storyline 360 to anything newer loses bookmarking after the user gets to some slides with quite a few user entry texts. This is across two completely different project files.

My client's LMS does not accept SCORM 2004 files, just SCORM 1.2.

If the suspend_data was working fine before then it isn't anymore since after the 3.36.21289.0 version.

Something has been broken and I'm now stuck with the January 2020 version and can't benefit from any new features/bugs fix. Digging through the log change should highlight what was changed. This needs resolving...

Many thanks.

Hi Courageous Success, I would contact support regarding your issue.

We have the problem solved for our platform, but in new courses it does not work. We have done the test in SCORM CLOUD and it does not work either.
In older courses, it does work correctly.
It is a serious problem because there are platforms that do not support SCORM 2004.

Hi Anna!

I see that my teammate Jopney is working with you in a support case. I see that Jopney has reached out via email. Have you received the email? If not, please check your Junk or Spam folder.

We are having this same issue. we are looking at a file that stops bookmarking in the middle of course. I have also looked at another file recently that exhibited the same behavior.

I did see that this new file had many unused variables that would end up in the suspend data string in the SCORM session save. I stripped these unused variables out, and am going to republish this to SCORMCloud to see if this makes any change.

We are publishing to SCORM 1.2, but I would prefer that we publish to 2004. But, this is out of my hands. I might suggest that to my bosses though.

Good morning, Mark!

Thanks for providing all of that helpful insight. Referencing Anna's case, we connected the problem to a past bug in Storyline 360:

• Behavior: SCORM 1.2 courses were restricted to the default 4,096-character limit even when increasing this limit in the LMS.
• Fix: This should be resolved in Update 41.

If you publish on a recent update and the bookmarking looks off in SCORM Cloud, don't hesitate to connect with us. We're happy to jump in!

Hello SibaPrasad, 

The issue described in this post has been fixed. Make sure that you have the latest version of Storyline 360 installed on your machine to get the latest bug fixes. If you're already using the latest version, try this workaround: 

• Edit the scormdriver.js file and change USE_STRICT_SUSPEND_DATA_LIMITS to false

If the workaround doesn't work, reach out to our support team by opening a support case for further assistance.