What are the things that affect resume where you left off and suspend_data?

Hey Rocio! You had the right idea to open a case. I see Gerald shared some really helpful information with you! I'll add his reply below for anyone else who encounters suspend data issues in the future.

–––

As a learner makes his way through a course, a compressed chunk of suspend data is sent to the LMS after each slide. This suspend data describes everything about the current state of the course, including the learner’s responses, his navigation history, object states, variable values, interaction results, and more. 

You can enable LMS debug mode to watch your suspend data flow back and forth between your content and your LMS. By doing so, you can verify that the data returned by your LMS upon resume is the same data that your content sent upon suspend—a common point of failure. Here's how enable debug mode in Storyline. 

You can more details here about suspend data and resume behavior here. 

Hey, Rocio! 

If you have a large course that exceeds suspend data limits, here are some suggestions for correcting it: 

1. Disable the resume feature in Storyline. 
2. Reduce the number of slides until the resume feature works as expected. The limit will vary, depending on a variety of factors. You'll need to test your content in your LMS to verify. 
3. Republish your course for SCORM 2004 3rd Edition or 4th Edition, both of which support much longer suspend data.

Let us know if you need anything else! 

Thanks for pasting the “official solutions”, but that’s exactly why I started this discussion. Those are not working for me as stated at the beginning of this discussion.

I am looking for additional help, potentially from users that have the same problem; there are many. 

1) Publish to SCORM 2004 - Not an option (our LMS only supports SCORM 1.2)

2) Remove the functionality - Not a solution

3) Delete some slides - If it was just the number of slides that determined the length of the suspend_data element of the Storyline SCORM package, none of my courses would work. I have courses with more slides than this one, and none of them have these issue. Deleting slides seems like an over-simplified non-realistic fix.

Can you possibly split the course into two courses--like Part 1 or Part 2?

Does your LMS support multi-modules?  Basically the same as above except it's all "one course" with two modules the learner has to complete.

Looks like you’ve tried the solution I’m about to recommend  Rocio and are not seeing complete success.   I had this problem some time ago, was publishing to SCORM 1.2, and solved it by setting all slide layers To “reset to initial state” .  I also do a run through of all slides and layers at the completion of a project to make sure they are all set this way.  I’ll only change this setting for a specific layer if the functionality I’ve created Requires it  (I rarely have to do this). I also delete any unused variables and unused master and feedback templates....these last two may not have anything to do with suspend data but are just good housekeeping to keep file size and complexity down to minimums. Hope you get breakthrough soon. Best wishes. 

set slides to reset to initial state can reduce the suspend data. Peter gives a really good suggestion.

Which LMS is it on often you can override the score 1.2 limit 

Do you have any custom interactions in the course?  From my testing, SOMETIMES they can really balloon resume data.

Can you share your .storyfile or is confidential?

If you are really set on one course, you may want to enable debug mode and after each slide, get a count of the resume data string length.  At least you may get a more definite idea of which individual slides are adding the most resume data.

For the longer haul, you might want to consider upgrading your LMS to a newer version (if there is one) or another one that supports SCORM 2004 3rd or 4th Edition and Tin Can/Experience (and in the way that you want it, too--but that's the subject of another discussion :) ).

Thanks for all your help.

On to something now. Seems like is impossible to have Resume functionality AT ALL on any type of graded style questions.

I published the Assessment Scene as a standalone SCORM package and enabled debug mode.

The scene only contains the following:

   - An intro slide,

   - 12 questions

   - Results slide

The Intro slide is set to Reset to Initial State whereas the questions are set to Resume saved state.

STILL FAILS: suspend_data blows up right about question 5-6.  

None of my questions are text based. I only have T/F, single select, and multiple choice. They are all graded questions, no free-form.

I would think that something that simple would not fail and Resume Functionality would be able to work, but apparently it doesn't.

Either our set-up on the questions is completely wrong or Articulate is extremely inefficient when it comes to question and how it compresses suspend_data.