"Resume Saved State" - no longer works if Next button disabled when timeline begins?

Hi, Kat -- Thank you for reaching out and sorry to hear of your troubles! May I ask if you are finding this issue when you test your course in the intended environment or where the course will ultimately be accessed by learners? And have you taken a look at the troubleshooting steps listed here to see if you find improvement? If issues persist and you are only noticing this behavior after Update 9, you would be welcome to connect with our Support Engineers, as well. 

Hi Kat,

There is a known issue right now with the next button returning to a disabled state on a revisit to the slide, even if it's using the "resume saved state" set up. You can see similar discussion of this issue here and a few suggested ways to modify the slide to allow it to work normally such as using a variable.  

I'll include this thread in the report filed with our team so that I can share any updates with you here once they are available. 

Hello!  Are there any updates on this issue?  I'm having the same problem of a Next button returning to a disabled state even though I have Resume saved state when revisiting. 

Hello Michele - I do not have an update at this time, but I do appreciate you popping in to let us know you are being impacted by this. We are trying to do better about prioritizing based on user impact.

You have a couple options for workaround:

1. adding these triggers to the Slide Master:

   • Change state of next button to disabled When the timeline reaches 0.5 seconds.
   • Change state of next button to normal When the timeline ends.
2. utilizing variables as shared in this thread

Any updates to this?  It seem like a pretty straight forward issue; if you set the slide to "Resume saved state, it shouldn't fire a trigger that already played the first time.

Hey Michael!

Since this is an older thread, I'd like to start fresh. It sounds like you're having some trouble with the Resume Saved State setting. 

Can you help me with a few more details?

• What version of Storyline are you using?
• What happens when you revisit a content slide? Is the timeline starting over from the beginning?
• Does this problem happen when you're testing the course in Storyline Preview mode?

I am experiencing the same issue. I am using the latest version of Storyline 360. In my slide, there is a trigger that says, enable the next button when 3 objects state are visited. When the slide is replayed, the 3 objects onscreen appear visited, and the timeline shows it is at the end, but the next button does not enable until you click on one of the objects that are already visited again. I tested this in Preview and published online in Articulate Review.

hi,

This is very common issue even in programming. Please check the triggers who executed first.
It is safe not to execute all triggers to "When timeline starts" event. Try to change other trigger to "When timeline reaches to 0.25s if you have condition. Because not all states, variable values are available at the same time when timeline starts. That is why we need few seconds to make the variable value, states are available. :)

Hey Shawna,

It looks like Rex has popped in with some helpful advice.

If you need us to take a look at your .story file, feel free to share and just let us know what slide to focus on :)

Hi,
I'm having the same exact problems.

• Change state of "next button" to "Disabled" When timeline starts
• When revisiting: "Resume saved state"
• If you go back one slide, the first trigger will fire anyways, and disable the next-button. the user is then stuck in the course, and the only way to advance is to restart the whole course and never click the back-button.

How come this is still not yet fixed???