Storyline Suspend_data decipher

Hello Doron!

Sorry to hear that you spent days experiencing an error before reaching out. I'm sure that is frustrating.

We do have an LMS Debug Log to assist users in troubleshooting and typically advise testing the content in SCORM Cloud as well to see if the issue is able to replicated in a standard environment.

If you find that the issue is within our software or have additional questions, you are always welcome to work directly with our support engineers as well.

Just stumbled upon this conversation in search of the real point of the debug log if you can't decipher the data string(s.)  I am in that situation now.  I am looking at both debug and LMS course transaction reports from a sample course published in: SCORM 1.2, 2004 - 3rd and 4th ed.

I want to see the data interaction between the course/player and the LMS to see what is the most efficient platform.  I haven't even worried about xAPI yet.  I've been able to parse the debug and report data, but not make sense of it without the "decoder-ring."  

In reference to David Keeling's request I believe the standard for SCORM 2004 will do just that.
In the parameters it has one for course tracking and completion and one for tracking quiz completion.

SCORM1.2's (lesson_Status) was split into 2 parameters in SCORM2004; ‘completion_status’ (completed/incomplete) for the course and ‘success_status’ (passed/failed) for the quiz. Now whether SL sends both calls is another matter which is why I am attempting to decipher the debug and lms data reports.  Is there any way to read or decipher the debug log? 

Hi Paul, 

Our  LMS debug mode will let you see the data being passed from Storyline to your LMS, but the suspend data/bookmarking elements are compressed and not human readable. The other data should be there for you and if you're having difficulty deciphering it our Support team is happy to help! 

You'll want to upload a copy of your .story file, the debug log and a link to the course if your LMS (in you're able). They'll take a look at testing it and be in touch with you via email as soon as they can! 

This is a HUGE need for us. We have active users going through our courses and so when we update a course, we don't want to destroy their learning experience. Right now, there's no way for us to update our courses without impacting hundreds of our students...

Thanks for this info! This was really helpful. I was able to determine who skipped to the test on a module after the fact by finding a pattern in the Suspend Data. 

I found that if this string was present, the person "tested out:"

01012010130111301213013130141301513Ub

Basically

01012 <- First slide
01013 <- Jumped to quiz
01113 <- Quiz question 1
01213 <- Quiz question 2
01313 <- Quiz question 3
01413 <- Quiz question 4
01513U <-Result slide (followed by a U I think means they didn't navigate to any slides after it, as it starts a new section of the Suspend data).