Problem with Resume saved state!!!


"Resume saved state" is a great option when the user revisits a slide and I do not want to show the effects or animations again and again. But I have a problem. I made a slide with three layers (plus the base layer). All were set to "Resume saved state". When I revisited the slide the first time, no problem, but when I revisit a second or third time, the second and third layers disappear. Can anyone tell me what is the problem?

Thanks very much!

13 Replies
Chris Brooks

I too have a problem with 'resume saved state' in Storyline :

I am asking my usesrs to choose from a list of words on a slide.  When they click on the word it changes state and takes them to another slide.

Once they have finished on that slide they return to the original slide with the list of words.

I have set the slide to resume saved state but it does'nt save the changed state of the word that was clicked.

They have to revisit this slide 9 times and I would like to show which words they have visited and which they still need to visit

Any ideas what I am doing wrong ?


Christine Hendrickson

Hi Chris,

Does this work properly when you're previewing the project? Also, how are you publishing/viewing the project? Are you publishing for Flash, HTML5, Web, LMS, etc.? Are you viewing the project after its been uploaded to a web server or LMS?

Also, can you confirm you're using the most recent release of Storyline? To find this information, please click on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), please download and install Update 2 from the link below. Once you've installed the update, please republish and test your course.

Articulate - Download Storyline Update 2


Chris Brooks

Hi Christine.

We found out what the problem was with the resume saved state.

We were changing a state AFTER the change of slide,

so the triggers looked like:

-Change slide

-Change State of...

so the slide changed before the change of state could actually occur... simple now we look back on it,

So we simply moved the order around. hope other people can learn from this

Scott Wiley

Due to the amount of data Storyline sends to the SCORM suspend_data field when choosing to resume saved state, I typically will use custom variables and triggers to achieve the same thing.

For instance, you could create a true/false variable for each button, set to false initially.

Add a trigger to each button to first change its associated variable to true, before navigating to another slide.

Create base layer triggers to change each button to its visited state if its variable is true when the timeline starts.

Set slide to return to initial state when revisiting.

Tom DiCrecchio

In this example, its more a Layer issue within a slide that is using SLIDERS that allow you to advance to another layer once you have viewed all of the SLIDER elements (set with Variables)

I am referring to a Slide that is using a SLIDER on the base layer and that is showing another layer once you have viewed all of the elements in the SLIDER. When you are using a Custom button on that layer to nav back to Resumed State of the base layer (the one with the SLIDER), the SLIDER doesn't show the last tem, instead it shows the last SLIDER position but not the text associated with the last SLIDER position (which you would expect).

I tested this using the DEFAULT Next and Prev and CUSTOM Next and Prev buttons.

The above example works with the DEFAULTS but not the CUSTOM buttons.

However....Since my company wants to use Custom buttons the workaround is simple:

Create a separate slide instead of using a layer to appear after the SLIDER conditions are met.

TO recap, if you are trying to use CUSTOM nav buttons on layers on a slide that also uses SLIDERS, the Resume Saved State wont work. Make a new slide!






Ashley Terwilliger

Thanks Tom for the recap of the situation and how you went about to resolve it. If it's ever something that you'd like our team to take a look at in terms of a possible bug please don't hesitate to share it here using the "Add Attachment" button or you can also send it along to our Support Engineers using the case submission form here.