When revisiting a completed module it prompts to resume, but goes to the same screen every time resetting the module from that point.

Hi Bex,

Thank you for the description of what you are experiencing along with the troubleshooting that you've done.

Based on the description, it sounds like you're running into suspend data limits, but you mentioned publishing to SCORM 2004.

• How did the content resume when published using SCORM 2004?
• Do you experience a similar issue when testing in SCORM Cloud or just within your LMS?

Your LMS may be treating your course in review mode, which you can read about here.

Hi Leslie

Thanks for getting back to me.

When I published in SCORM 2004 it no longer prompted to resume and simply reset the module when revisiting.

I haven't tried publishing within SCORM cloud only within my own LMS.

Thanks

Bex

Hi Bex,

You can set the resume behavior within Storyline as shown here, but often there is an additional LMS setting. I'd check with your LMS admin to confirm, and let us know if you're able to test on SCORM Cloud. It's free up to 100MB, and will help narrow down the root of the behavior! 

Hi 

Our LMS provider was able to tell me that SCORM 1.2 had reached it's character limit (I think thats right) which is why it was bookmarking at a certain point.

So I now need to publish the module in SCORM 2004 - which as I mentioned keeps resetting the module.

This is what happens:

I publish the module in SCORM 2004 4th edition - with prompt to resume set. I recently updated Articulate 360 so I'm running the current version. 

I have five sections to the module and I can exit out after each section has been completed and I am prompted to resume at the right point every time - until I complete all of the sections. So the module is complete.

When I exit the module - when it has been completed and then revisit it, the whole module resets to the beginning and I am not prompted to resume.

Any help/ideas would be appreciated.

Thanks

Bex

Hi Bex,

I haven't run into that behavior before, but we'd be happy to take a look! Have you looked at testing it within Scorm Cloud which is a standard for LMS testing? It'd be interesting to see if the same thing occurs there or it's restricted to your LMS. 

Let me know and our Support Team is around to help with any testing too! 

Hi Ashley

Unfortunately I'm a bit stuck as i can't share the content outside of our organisation. I just wondered if anyone had any insight really.

The module is quite large at 1.4GB so I am trying to reduce the size of the module to see if this will make a difference.

Thanks

Bex

Hi Bex,

I understand, let's see if I can share some additional information that may be helpful for you.

It sounds like the resume is not working as you expect once you've met the completion requirement for the course. Most LMSs consider a course to be in review mode after the tracking requirement has been met. In review mode, resume data is no longer sent to the LMS, which prevents learners from accidentally changing their course status back to incomplete. See this article for more information and details to adjust if needed.

Hi Leslie

I just wanted to say thank you for pointing me towards this article. It was very helpful. I changed the reporting option to Passed/Incomplete as recommended, and now the module now prompts to resume after completion. 

Thanks

Bex

Glad that was helpful, Bex. Thanks for chiming back in to share an update :)

Hi, I am experiencing this exact issue whereby the Resume function (set to: "Prompt to resume") does not work (ie after closing then re-launching the course, the user is not prompted to "resume or restart") with a course published with the following settings:

1. LMS: "SCORM 2004, 4th edition"
2. Tracking: "Track using quiz result"
3. LMS Reporting: “Passed/Incomplete” and
4. Resume - On restart: "Prompt to resume"

I can see from this and other articles that this "bug" has been a known issue for years now and appears to be a result of how SCORM 2004 interacts with the tracking slide.

This is causing us a MAJOR problem because it means, as a work around, we have to split the course up into two files - one in SCORM 2004 without a tracking slide (to benefit from the larger data limit in SCORM 2004) and the other in SCORM 1.2 with a tracking slide (to enable graded assessment). This, in turn, requires a lot more complexity in setting up in the LMS to ensure all screens are viewed and confirmed as such by the LMS (I haven't figured this stage out yet, but am confident it can be done).

Surprisingly, the problem is partially avoided if the course is deployed to an LMS via SCORM Cloud - the LMS records the grades, but SCORM Cloud does not. I assume the "bug" is prevented from having its effect until the point where the LMS reports back to SCORM Cloud. 

Please try to fix the issue!

If a fix has already been developed (and I have missed it in my research), someone please let me know. Thank you!