Forum Discussion
How does Storyline Resume?
When storyline asks you if you want to resume where you left off, presumably information about where you were last time must be stored. Where is it placed? Is it in a browser cookie?
John.a.
- ChristineHendriFormer Staff
Hi John,
I believe (and I may be wrong) that it depends on where you're hosting the course. I believe by default the content is stored in a Flash cookie.
Depending on which resume option you choose, if you choose "Always" or "Prompt" for example and you're using an LMS, you can choose to have your LMS manage the resume data if it's able.
When the option for "When running in LMS, ignore Flash cookie" is marked, if you upload your published course to an LMS that supports resume data, the course will use the LMS bookmark rather than the Flash cookie that would normally be used. If you upload your course to an LMS that does not provide a resume bookmark, the course will use the Flash cookie as usual.
If you can share a little more information about how you're distributing your course, maybe the community can give you some additional details on this.
Thanks!
- JustinWilcoxCommunity Member
Hi John.
Christine is correct depending on what you are publishing for:
- Web output is handled by a Flash cookie.
- LMS output is ideally handled by the LMS using the suspend_data we send. If you uncheck the option to ignore the Flash cookie, though, this could cause issues with the resume so I would not recommend doing that.
- Articulate Online is handled through suspend_data as well.
- CD is handled by a Flash cookie.
- MicheleZemourCommunity Member
Hello Justin,
I have the same problem concerning an erratic resume function of Storyline, on my LMS
When I publish using the Web option, the resume is working fine.
I tried to view the published files of my project to look for this suspend_data: where can I find it?
Thanks for your help.
Michèle
- JustinWilcoxCommunity Member
Hi Michele.
Suspend data is sent to the LMS when you publish to the LMS and load the content into your LMS. The content will communicate this information at that point. I would refer to this article which helps troubleshoot basic LMS issues. If you can describe in more detail the issue you are experiencing, this could help us figure out what's going on. What LMS standard are you publishing for? What exactly is happening when you try to resume?
- MicheleZemourCommunity Member
Hi Justin,
Thanks for your answer!
I delete the bowser cache and it's seems to resume proprely. Do you think though I should investigate more ?
- ChristineHendriFormer Staff
Hi Michele,
If you deleted the cache and that's fixed the problem, you should be good to go.
However, if you want to double-check to make sure it's working properly, you could try running the project in a different web browser (preferably one that hasn't been used to open the course, or clear the browser's cache before launching the course).
Let us know how it goes!
- JerineSebastianCommunity Member
In such a case, do the students have to clear cache every time? I'm facing this issue where it always shows the previous version of the course unless, I delete history. Doing this every time would be cumbersome for the students. Where is the problem? With Storyline or with the LMS. At least that would tell me where I need to fix this.
Thanks.
Hi Jerine,
Do you mean the previous version as in where the user left off - or are you overwriting a previously uploaded version of the course? The latter you'd want to ensure that they clear their cache to access the latest version. As far as the resume, if you've set the course to always resume or prompt the user to resume - they'll be able to pick up where they left off unless they were to clear our their history. If you don't want them to resume - you could choose to "never resume" as the option. You will also want to check with your LMS to see if they have a resume setting you need to change.
- MarcusLouvetLarCommunity Member
Hi, my issue is this: The course im publishing is for web, since i dont have an LMS that will give me SCORM-data.
But the users are going to view the course on their job computer, which mean that, lets say 5 different people will go through the course. The prompt to resume or always resume option works if a single user is on one computer, but if for example user 1 pauses the course midway through and the next day user 2 is gonna start from scratch, then he or she is prompted to start from where user 1 left off,
Is there a workaround here?? open to any and all suggestions.
Using storyline 2.
- johnfaulkesCommunity Member
Marcus, I think what you mean is that you have multiple learners taking the course on the same computer? if so you're definitely going to have this problem, without them accessing an LMS version.
The most brutal solution is to set the SL player to 'Never resume', and have a very clear menu system that easily allows learners to recall where they were, and select that section.
A much more elegant solution would be programmatic: you could build a login page at the start of your project, and fill an SL variable with (let's say) their email address that they enter. Then you know who they are. It's a start but only a small step on a long journey..
As they progress through your course for (say) each section you could fill a progress variable, but trouble is you'd need a progress variable at each point, for each user.
When anybody restarts, you could set a few conditions in a trigger- testing who they are, and their progress variables as set, then jump them to that latest set point.
All in all? It's probably not worth the effort to do this!!
- DanielFillionCommunity Member
I'm facing this issue and am willing to tackle it. When you say "Progress variable", are you referring to the data put out by "SetDataChunk"? I am saving this value to an SQL table, and recalling it using GetDataChunk, however it does not cause the Module to resume. The module does run the GetDataChunk function prior to starting, but proceeds to start at the beginning. Thoughts?
- MarcusLouvetLarCommunity Member
Thanks, yes i was pretty sure this was the case, the workaround described is too much work for me :)
Thanks anyway!