What are the things that affect resume where you left off and suspend_data?
May 24, 2019
I've spent a significant amount of time trying to figure out what are the things that affect the suspend_data element in Articulate.
I have a course in which the Resume where you left-off functionality doesn't work.
Once the course reaches a specific slide, it always comes back to that slide and never resumes past that point, even if I exit the course from another slide or a different scene. It always just saves progress up-to the same specific point.
I published the course with "On Restart: Always Resume" and "On Restart: Prompt to Resume" and tested both configurations both on SCORM Cloud and our LMS and get the exact same behaviour. So I know this is not a "restriction from our LMS"
I submitted a ticket with my source file, and the only options that I've been given so far are:
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.
I'd like to know if someone has an understanding of what are the things that affect the suspend_data element.
I was able to set up an LMS debug file and observed how the suspend_data element grows as I move through my slides - and my course does reach the SCORM 1.2 limit of 4096 and spits the intSCORMError = 405
I tried to set many slides and layers to Reset to Initial State, which seem to help a bit. It allows a bit more room for suspend_data to grow, but it simply makes another slide the one from which you have to resume later in the course, Still doesn't work, but at least "more" progress is saved.
It would be good to hear if anyone has found other things that have helped with the resume where you left off non working.
Seems like there are several of the same issues without a solution.