Not saving progress

Hi Guys,

We are experiencing this weird problem on our LMS, where the progress can't be saved past some point, and the presentation resume only at a certain slide (always the same slide).

For example, if you reach slide 235 and close the presentation, once resume you are at slide 153.

At the same presentation now you reach slide 453 and once resumed you are back at slide 153.

Always resume function is selected.

Any ideas how to fix this issue as it is very frustrating to the users.

Thanks in advance.

15 Replies
Katie Riggio

Hi there, Bobby. I'd love to investigate this with you!

First, let's test the course in another LMS environment like SCORM Cloud to be sure there's nothing wrong with the Storyline content. If the resume behavior works correctly there, then the issue is related to the LMS' output. Let me know if you need a hand with testing!

Additionally, let's check the SCORM suspend data limit. What version of SCORM are you using? 

Petya Zhelyazkova

Hi Katie,

Test the file in SCORM Cloud and the issue occurs again.

We are using SCORM 1.2, I never really experimented with other versions.

I published the same course in SCORM 2004 and tested in SCORM Cloud, but the resume function didn't worked at all and the course restarted from the beginning.

I have uploaded the file in the support section for you to review.

Let me know if you need anything else from our side.

Leslie McKerchie

Hi Rachel,

It looks like it was the solution for the users that reached out previously.

Are you running into a similar issue of the course resuming in the same spot for your learners?

Understanding the SCORM Suspend Data Limits may shed some light on why this solution worked above.

Let us know if you're seeing something different. We'd be happy to help you as well.

Rachel Crabtree

Hi Leslie, 

Funnily enough I just happened to be reading that article separately from this thread.  Unfortunately the article mentioned:

"Because suspend data is compressed to allow for more robust storage, the suspend_data string in an LMS debug log isn't human-readable. That is, you won't be able to decipher it"  

So instead of being able to confirm that the problems are indeed related to suspend data through a de-bug log it suggests to:

  1. Disable the resume feature
  2. Reduce the number of slides and reload - then repeat until it works as expected
  3. Publish to 3rd/4th edition

We are in a live production environment with hundreds of users assigned the course and we cannot troubleshoot live (i.e. stop the resume function or repeatedly pull down and reload the course with a different number of slides).  Also the bookmarking issue is inconsistent and not reproducible across users.  We have been publishing to 3rd edition, but 4th edition appears to be compatible so here on out I will publish to 4th. 

Are there more concrete guidelines to stay within the technical limitations of the 4th edition suspend data feature?

Thanks for any advice you may have :)

Rachel

 

Leslie McKerchie

Hi Rachel,

Both the 3rd and 4th editions have the same amount of characters, so your current setting should be good.

  • Can you explain more about the issue some of your learners are seeing? For example: Is it resuming on a specific slide for them?
  • Is this happening with a specific:
    • scenario? For example: User has completed the course and is re-taking again.
    • browser?
  • What LMS are you using?
Eike Heinrichs

Hello people,

very interesting that also others have to deal with the "not saving progress" in articulate storyline with a scorm 2.1 output. I write here, because we are dealing with the same problem, but with the difference, that the point of "not saving progress" is already at slide 15 out of 48. Which seems very strange, because it is so early, that the suspend data reached is limit. Unfortunatley our client wants/needs its course in scorm 2.1 and also with the resume function. So what can we do here to solve the problem on another way? As I read here, at some other guys the problem with the suspend data occurs at slide 135. Because our course is only 48 slides long, I expect, that articulate can handle it in scorm 2.1 too....

Very happy to here from anyone here, because we are very frustrated about it and deadline is coming soon. Uploaded the file to articulate support yesterday, but didn't receive an answer yet.

Thank you in advance.

Eike

Ren Gomez

Hi Eike,

Thanks for reaching out, as well as starting a case! It looks like you're continuing the conversation with my teammate, Chester. I'll be sure to let him know the details you shared here, as well as have him test the file you shared to see if he can offer further suggestions.

Be on the lookout for a reply soon!

Lauren Connelly

Hi Emily!

We are happy to help! It sounds like the resume behavior is different when using SCORM 1.2 and SCORM 2004. 

Your LMS might be imposing limits on suspend data. Older LMS specs have outdated restrictions on suspend data which affects the resume behavior.

Are you publishing using the latest edition of SCORM 2004?  This article explains suspend data in greater detail.