This may be a silly question, but how does prompt to resume work without an LMS? Isn't the resume data a SCORM value? What happens to SCORM values without an LMS to capture them?
My guess is it has to rely on a cookie of some kind, which is really sketchy to rely on these days...
In order to replicate true resume functionality without an LMS you'd have to send a variable value (slide number or something) to a database, Google spreadsheet, etc, along with a user name (which you'd have to prompt for).
When a user returns you'd have to check your database for that user name (I guess it would have to be unique) and return the value of the variable, then figure out how to get them where they need to be in the course based on that variable.
If it is indeed a cookie, prompt to resume will not occur without the cookie. This could occur when a person logs in on a different computer or after clearing browser history to include cookies.
If it is indeed a cookie, prompt to resume will not occur without the cookie.
This was the problem the original poster has... occasionally the course will freeze on resume, forcing the user to clear browser cache, thereby deleting the resume info and forcing the user to restart from the beginning.
You're right, Storyline will rely on the browser cache and cookies to keep track of that resume data if you've only published for Web and are hosting on a server. Have you spotted any trends about the browser(s) learners are seeing the freeze within? Also, can you check what update of Storyline you're using?
8 Replies
Hi John,
Thanks for reaching out and sharing what you are running into.
Is this behavior that you are able to replicate?
You mention that it's happening in different browsers, but is it a particular slide in the course that's consistent?
What is so frustrating is the random nature of this problem. Different browsers, courses and users.
I am hoping someone has advice as to how to start narrowing down the possible causes.
This may be a silly question, but how does prompt to resume work without an LMS? Isn't the resume data a SCORM value? What happens to SCORM values without an LMS to capture them?
My guess is it has to rely on a cookie of some kind, which is really sketchy to rely on these days...
In order to replicate true resume functionality without an LMS you'd have to send a variable value (slide number or something) to a database, Google spreadsheet, etc, along with a user name (which you'd have to prompt for).
When a user returns you'd have to check your database for that user name (I guess it would have to be unique) and return the value of the variable, then figure out how to get them where they need to be in the course based on that variable.
Actually, the resume prompt has been working really well for us. We only publish for the web.
I suspect a value is left locally, but I can not find any technical info.
This is interesting, I have never tried this.
If it is indeed a cookie, prompt to resume will not occur without the cookie. This could occur when a person logs in on a different computer or after clearing browser history to include cookies.
This was the problem the original poster has... occasionally the course will freeze on resume, forcing the user to clear browser cache, thereby deleting the resume info and forcing the user to restart from the beginning.
Hi John,
You're right, Storyline will rely on the browser cache and cookies to keep track of that resume data if you've only published for Web and are hosting on a server. Have you spotted any trends about the browser(s) learners are seeing the freeze within? Also, can you check what update of Storyline you're using?
Storyline 360, build 3.31.19951.0 is the latest update within Articulate 360, and Storyline 3, build 3. 3.7.20003.0 for our perpetual build of Storyline was released today.
This discussion is closed. You can start a new discussion or contact Articulate Support.