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

Did some more searching. The "timeline starts" trigger is supposed to always fire? It cant have been like that since the beginning, as I've uses these functions before. 

I even tried using "when timeline reaches 0.25 sec" and "0.5 sec", and "2.0 sec", but its still returning to disabled instantly upon going back one slide. Are there known bugs to this at the moment? Because I cant seem to find a way to keep the next-button disabled untill the user have completed the requested actions. Going back to this slides renders the user unable to ever move forward again.

Even quicker workaround:

Change state of next button to Disabled
     when the timeline starts
          if <Object that needed to be visisted to advance>'s state is not equal to Visited

But its still a workaround, and I should have to do this for a basic behavior like this. 

So, as of now, storyline does not support "Prevent user from moving to next slide until the user have completed an action on current page. And also enable the user to revisit this slide without getting stuck forever"? And this is intended as "by design"? Weird decision :P

Or for that matter;
Its not possible, by default, to perform any actions when timeline starts, only the first time the slide is viewed, even if it's set to resume saved state. Cant possibly be the intended way this should work. :P

I also have trouble believing this would be by design.  If so, could you please inform us of the intent of such a design decision?  I can't think of any reason anyone would want to resume saved state except for some of the triggers. 

If this is truly the case, then there should be another slide revisiting option called, "Resume most of the saved state" for the current way it acts.  Or leave "Resume saved state", as it is and add another option called "No really, resume saved state" that will actually resume the saved state.

The purpose seems straight forward, you either want the slide exactly where it was when the learner left the slide or you want it to reset and start from the beginning.

Hi Stian,

I'm glad that you were able to figure out the correct triggers needed for your course.

Each time you visit and re-visit a slide, the timeline re-starts.

The solution that you've found is similar to the instructions that we share here when you wish to restrict navigation with the prev/next button for some slides.

@Michael: Indeed. On the serious side, for this to make any sense at all, there should be another trigger. One is the "when timeline starts", and one should be "when slide loads".

@Leslie: The timeline might re-start, but it should not trigger the "start", as it never starts upon resuming saved state. It resets, but should not start. And if it does not start, it should not trigger the "when timeline starts" action.

No, in the example you provide there are no "logic" behind the state. It simply overrides the disabling of the next-button anytime you visit a slide with this trigger, even if the user have not performed the requested actions needed to advance to the next slide.

My issue is that I see no logical reason for why a trigger named "when timeline starts" to fire, when revisiting a side with saved state. 

The current behavior will also prevent me from other actions tied to the timeline, if the timeline is reset to start even though its set to save states. Say I have a slide, where at 5, 10, 15 and 20 sec I pause the timeline. An individual animation happens inbetween these 5 second gaps. When the user presses a button, the timeline resumes, and shows the next animation. If I only click the button twice, go to the next page, and come back, its all reset? Even with the save states enabled? I would then have to do 2 empty clicks and wait 10 seconds, before I could continue with my 3rd animation?

Hi Stian!

I've passed your comments along to our Engineering team. I will report back if I hear of additional information to share. Thanks for sharing what would be a beneficial addition to your build!

Thanks. :)

"When timeline starts" Should in my head only fire when the timeline actually starts.

The current behavior could be called "When slide loads" or "When timeline loads" or similar, to distinct it from always happening, og only first time visiting if slide is set to resume saved.

Quick question, outside of this. If I have a result slide, and want to submit a lot of questions. This could take some time to reach the LMS? Will the next action wait for the previous to complete?
If I have "Submit results xxx when timeline starts", and then a "Jump to slide Next Slide when timeline starts" following. Would it wait for the submit action to complete, or would it jump as soon as possible, possibly aborting the submitting data?

Hello Stian!

I would recommend adding a results slide instead of a "Submit results" trigger. This way the LMS will track the score from your course without any extra steps.

If you're going to add a "Submit Results" trigger, I would recommend attaching it to a button. This will create a more seamless process.

As of 2021, it's still a thing. Considering that this is an over five years old problem with workarounds that only sometimes kinda works if storyline feels like it, a basic functionality issue is clearly not a priority.

Still an issue in 2023. I am hoping this bug gets escalated since working around variables is not always an option when working on larger projects. 

Thank you!