"Resume Saved State" is not saving State of Next Button when returning to slide

Apr 15, 2019


I have a slide that hides the Next button when the Timeline starts, then brings it back to Normal when the users Visits 3 objects (and their States change to Visited). I have the slide set to "Resume Saved State" for when the user returns.

However, when the user does return to the slide, the Next button is still hidden and the user has to click the last object (whose State is still Visited) in order for the Next button to appear. I need the Next button to stay Saved along with all of the other States when returning to the slide. Any help?


23 Replies
Alyssa Gomez

Hi there, Shauna!

Our team is investigating an issue where the next button remains disabled or hidden on a revisit to the slide, even when the slide properties are set to Resume Saved state. 

To workaround it while we continue investigating, look at adding these triggers to the slide or the Slide Master:

  • Change state of next button to hidden When the timeline reaches 0.5 seconds.
  • Change state of next button to normal When the timeline ends, on the condition that the objects are visited. 

We'll keep you posted on the issue here! 

Ronda Otey

Okay, I looked back at one of my old Storylines from my last project manager, she is a genius by the way with variables and triggers here is what works:

EnableNext1 is the variable and it is set to False.

1st Trigger

Set EnableNext1 equal to True when the state of (enter you object or objects) are Visited

2nd Trigger

Change state of the next button to Normal when EnableNext1 changes if EnableNext1 is equal to True

3rd Trigger

Change state of the next button to Normal when the timeline starts if EnableNext1 is equal to True

Hope this helps!

Tori Jacklitch

I am having this same issue. The variable work around is not as great for me as I have 12 different buttons that need to be in the visited state before the next button can be enabled. Any update on when this issue will be resolved? I need it to resume the state even when the learner returns to the slide WITHOUT them having to click on an already visited button again. Please help.

Ashley Zuco

Has this issue been resolved? It is a pretty common programming ask from clients (to require users to click all buttons). I programmed my entire course already with the "change state of next button to disabled when the timeline starts" and "Change state of the Next button to Normal when the state of ____ is visited" and did not realize the next button stayed disabled upon returning to the slide. I  understand the variables and triggers I can use to resolve this, but I really don't want to have to go back and reprogram every slide. Is there a quicker fix than deleting these triggers and starting over? Thanks!

Lauren Connelly

Hello Ashley!

I'm happy to help! It sounds like there might be something specific in your file affecting the state of the next button. 

With your permission, we'll take a look at your project file to investigate what's happening. We'll delete it after troubleshooting. You can upload it privately here: Support Upload Link

When you upload the file, we'll receive a notification. After reviewing the file, we'll get back to you as quickly as possible.

Kelly Gross

I am also having this issue.
Per Walt's comment, I have my slides set to "Save state on revisit", so that's not it.

The workaround Alyssa Gomez posted above (setting the next button to false until timeline reaches 0.5s) works, but if this is a bug, as was referenced above, I'd love to know when it will be resolved...

Oddly, before adding the 0.5s "fix", if I went back a few slides more, then clicked the next button several times in a row, it would work. 

Even more oddly, if I did that really fast, I could even sometimes get it to advance PAST where I'd been (so avoiding any variable triggering at all).  

Would love to have some definitive answers from Articulate as to what's going on. ;)

Thank you! 

Lauren Connelly


We'd love to help! I looked at similar cases where others are running into this same snag. It looks like our Support Engineers were able to offer specific troubleshooting steps and a solution after looking at the affected file. Are you able to share your file with our team? If so, here's a secure upload link. We'll let you know once we receive the file and begin troubleshooting. 

Judy Nollet

FYI: There is definitely a bug, because triggers set to execute when the timeline starts do re-execute even when a slide is set to Resume Saved State (i.e., to not replay the timeline).

Until the bug is fixed...

  • If only some slides should disable Next, use a condition on the trigger that disables it (as described above).
  • If all slides should disable Next until the timeline ends, just set the Menu navigation to Restricted. That automatically disables Next the first time a user visits a slide, enables Next when the timeline ends, and keeps it enabled when the user revisits -- all without the need for triggers.

Note: You can override Restricted navigation on an interaction slide by adding your own triggers to control the Next button.  

Kelly Gross

Hi Lauren,

Thank you for your reply.
So, is it correct that this is a known bug? I wasn't quite sure based on what you wrote...
Thank you for the kind offer. However, as the 0.5s workaround is doing the job, I'd rather wait until the issue is fixed (I have more than one file impacted).
Thank you!

Leslie McKerchie

Hi Camilla,

I just responded to a similar conversation here.

Adding on to this conversation gave me another clue into what you may be dealing with.

We've consulted with our product team on the behavior where the Next button returns to hidden or disabled when revisiting the slide, and after careful review, we determined it to be by design based on the navigation features.

We recommend using the settings outlined here.

Karen  Kasper

Thank you, Ronda! Those triggers worked. It should be noted that you also need a trigger of Change State of Next button to Hidden when timeline starts if variable EnableState = False, and it needs to be above the trigger to change it to Normal when all objects are in a Visited state.