Suspend Data character limits

Hi everyone,

I just wanted to share a quick story (of our success) on how we managed to hit a wall, then find a solution concerning Suspend Data character limits within our LMS.

Backstory: My team develops online courses for those looking to get a state license (Real Estate, Construction, Health Insurance, etc.) in Florida. These courses can be upwards of 72+ hours of required online "class time" so the files can sometimes be quite large. We've been using Storyline 2 for a while and for this scenario we were publishing SCORM 2004 3rd edition Update 11 for HTML 5.

The Problem: We noticed that one particularly large chapter (Storyline project) was occasionally having some issues updating between the user and our LMS. The Suspend Data was corrupting though we weren’t sure why. From the student’s perspective, they would lose their place as if they hadn't even started the chapter. We could copy/paste in good code but I really wanted to root out the problem. The character maximum was not yet hit, but there was a trend of support calls for the courses that had larger Suspend Data results. Unfortunately I couldn't find anything other than SCORM has a natural limitation of 64,000 characters. I couldn't find out what it was for TinCan, but our LMS doesn't support that yet so it didn't really matter.

Details: I had one large file (625MB) that had 172 slides with 133 variables and was generating 22,767 Suspend Data characters. We also had another file (279MB) with 196 slide, 168 variables, but was generating 60,694 Suspend Data characters. While they were both large, it seemed that the smaller file was getting dangerously close to hitting the Suspend Data limit of 64,000 characters. It was also the one that we were getting the most support calls on. After spending some time with tech support, there didn't seem to be any documentation on which parts within Storyline 2 would generate more Suspend Data than other parts. For example, would the slide count generate more code than the number of variables? How about the number of layers vs. variable use count (variables replicated across an entire project)? Value variables vs. numeric variables?

Solution: After quite a long time of incremental testing, we determined that the stock buttons and check boxes within Storyline 2 = Danger Will Robinson. Each button and check box that we used straight from the Storyline 2 toolbar generated 6 separate states, many of which were identical to each other and went largely unused. Our courses are designed so much of the content is non-linear as we want the student to have control over the order in which they view the content whenever possible. Thus we needed to have buttons on each slide to allow this (this is why we didn't use the Next/Previous buttons in the player). I also noticed that when comparing the two projects mentioned above, I didn’t use the check boxes and all of the buttons I custom created for the course with the lower Suspend Data. After removing the unnecessary/unused states, the Suspend Data dropped from 60,694 to 19,945. WOW! What a difference it made!

End Note: I had trouble finding anything in the e-Learning Heroes community that specifically addressed the challenge of dropping the Suspend Data limit. Our hope is that this will encourage someone out there, and hopefully save them time. We love Storyline 2 and are not looking to change anytime soon. I'm not sure if the "code-behind-the-curtain" for the buttons and check boxes is written as efficiently as possible, but I do know that this solution helped us significantly.

 

8 Replies
Chris Williams

Thanks for adding the link to this thread Alyssa. We found that one and it was helpful when learning about Suspend Data and resume behavior. The challenge is what to do when you start getting close to the limit. My hope is my post will let people know of possible solution on how to "thin-out" the Suspend Data. Thanks again!

Chris Barnett

Thank you, Chris, for this post.  I got a lot out of it (including a laugh.. Danger Will Robinson!). We are (very unfortunately) limited to SCORM 1.2, which is really cramping my design-style :S  Glad to know these hints on creating my own buttons, etc. will save me some room!   BASIC QUESTIONS ALERT:  how do I get a character count on my project?!?  Exporting to Word creates images on the page, not countable words/characters.  

Chris Williams

Hi Chris. That's a great question. I actually had to call our LMS and ask them how. They created a report that showed me the count for each SCORM component between a date range. Once I could run the report as needed, I was able to determine the size based on each update release I had/have. Let me know if there is any other way that I can help!

Sent from my iPhone

Chris Barnett

Thanks, Chris.  We figured out how to get an (estimated) "character count" in terms of just letters/symbols/spaces on the slides: we used the "Translate" functionality (under "File") to export the project.  This creates a Word document, where typical word/character-counts can be determined.  However, the key to your insight is that the "character count" with reference to Suspend Data is MUCH more intense than just letters-on-the-slides.  Thank you!

Chris Williams

Hi Chris,

If I understand you, then yes the number of characters on the slide (1 paragraph or 2) is pretty irrelevant. The amount of objects and interactions is really what will count towards the Suspend Data. Here is something you can do thought to get an accurate count. Use the Debug log. It's a function that's built in to the published SCORM file, but is turned off. Here's a link on how to "activate" it: https://articulate.com/support/article/how-to-enable-lms-debug-mode. Since you're running SCORM 1.2, scroll down towards the bottom of the article. This should be used for testing only as it will force a pop-up box to launch. It comes with quite a bit of Gorp (code you could care less about) but it does show the Suspend Data. You'll have to copy/paste it into Word and do a Character Count but it will be accurate. Note: I learned that this grows with every single interaction so if you revisit a page, it will continue to grow - not by much, but something to keep in mind. Also, this is data that is compressed by Articulate so it is not decodeable by any engine you can find online. It will just be a long string of seemingly random alpha-numeric code. If you have any trouble, please let me know.

Ashley Terwilliger

Hi Chris,

We do always like to use the debug log to see information in regards of interactions being sent back and forth, but as you said - the suspend data is compressed and therefore not human readable. The article Alyssa linked to above does offer suggestions for limiting the amount of suspend data as well.