Restricted navigation not working in HTML5 output when course is resumed

Feb 27, 2017

Hi Heroes, 

I have a course which was built with Storyline 360 and published to LMS SCORM 2004, and I'm having a serious issue with the player in the HTML5 output.

My menu is set to 'Restricted', so that users may go back to previously viewed slides but not skip ahead in the course. This feature works well if the user takes the entire course in one session. However, if they log out of our LMS and come back to the training later, access to previously viewed sections is disabled from the menu and everything is now locked.

I have my course settings to 'Always Resume' on restart, so that is definitely not the problem. I also know this because the course progress is saved correctly, and the user is always able to resume the training from where they left off. It is only the player itself that is reset every time they log out and log back in, and they wer not able to click on any of the previous slides anymore. (I was able to replicate this in SCORM Cloud, too).

This is a huge issue, as it pretty much makes the restricted navigation option useless. If you have a course that is long, like ours, you know that most learners will not complete it in one session. Unfortunately, setting menu navigation to 'Free' does not help me either, as this is a compliance course that needs to keep users from skipping ahead. 

I have already notified the Storyline support team about this bug, and they were able to reproduce it. However, they haven't yet provided a timeline on when it might be resolved. 

Has anyone else encountered the same problem? If so, have you come up with any creative workarounds? I would really appreciate any input from the community, since I'm not sure we can wait months for it to be fixed. 

Thank you.  

36 Replies
Claudia K

HI Tristan, 

Thank you for your suggestion. I'm not sure what you mean about creating variables to jump through the slides. Are you suggesting that I create a custom menu? Otherwise, I don't know how I could use variables or triggers to update the menu. We already have a custom player, so users can at least go back to previous slides by clicking on the back button, but that still doesn't help if they want to go back to to a previous section. (We have over 200 slides, so that would be a lot of clicking!)

I have seen people do things with Javascript to modify the behavior of the menu, but I don't know how to do that. Do you have any experience with this?

Claudia K

Thanks, Tristan. Well, the issue right now is that, taking your example, the user couldn't get to slide 16 unless they clicked on the back button four times. And even then, I'm not sure how any variable or trigger could set the state of previous slides to viewed so that they could view slide 5, for example. The only solution I see here is building a custom menu, which of course would give me full control of variables to allow the user to re-visit previous sections. But the custom menu option would clutter the slide so much that we may just end up switching to Captivate instead. 

Kyle Main

I'm having the same issue.

Last year, this feature worked for "big company", now it's broken. 

When a user is on the last video (each video is 10min. long) and then closes out and comes back the awful user experience happens.

The user will return to the correct slide (so the resume feature for the player works), but now the first and 2nd slides are LOCKED.

There is not a way for the user to jump back with the menu.  We have already taken off the next and prev buttons because that was a request.

With 300+ separate lessons like this, we have a nightmare for users.

Please help me find a work around, we will have to open every single storyline file and add a workaround if there is even one that exists.

I hope it's a bug that can easily be fixed and included in a very near future.

If we were given an estimate on any of the bug fixes then we would know if we should wait a week to open, fix, and republish all the courses, or if we should take a week or longer doing this with a work around.  I hope this will show Articulate how an estimated timeline could really help all SL360 developers.

Claudia K

Hi Alyssa, 

I took a look at the example you posted in the other thread, and it is behaving as expected. However, I did notice one difference. Your published version is set to 'Prompt to Resume'.

However, when you change the player Resume settings to 'Always Resume' to avoid seeing the pop-up, that's when the problem happens. (I just tested both options and was able to replicate it that way) I'm happy to find that this alternative works. It's not ideal for us, but it will at least serve as a temporary workaround. Thank you. 

I hope this helps Kyle, and I hope it helps the Storyline team diagnose the issue. 




Alyssa Gomez

Hi Claudia,

Thanks so much for chiming in. I did some more digging, and you're right, there is a known issue with Storyline 360 where you cannot go back to previously viewed slides when course is resumed if navigation is set to "Restricted" and resume setting is set to "Always Resume" in HTML5. I misunderstood Kyle's resume setting to be "Prompt to Resume", but if it is set to "Always Resume," that would explain what he's seeing.

Kyle, can you verify what resume setting you're using? 

Kyle Main

This is helpful. Now I do not feel crazy.
I may be able to do this for 20% of the Storyline lessons if the client
will agree.

I had tested my template so many times with the "Prompt to Resume" and had
not seen this issue.

My client came back with a need to remove that pop-up because it gave a
false idea to our users that in a 20 minute video they could leave and
comeback to resume where they left off.

I know that is not possible now, so the client felt that it called
attention to the fact that the eLearning projects to not work.

I set to the "Always resume, because there was about 20% of the 300+
lessons that had more than 1 slide with multiple videos. The Always resume
feature was a nice way to let them at least go past the first 20 minute

FYI, I know a video ove 3-5 minutes is dumb, but they already have hundreds
so breaking them up is not an option without an investment in the old old
content. New content is the plan going forward.

Claudia K

I know exactly how you feel, Kyle! I was starting to wonder how this bug wasn't a big deal to anyone else out there other than me. I'm glad this workaround is helpful for at least a portion of the courses you're working with. 

I also wonder if you could still get the slide to resume from where the learner left off by playing around with the slide properties and setting the 'when revisiting' option to 'Resume saved state'. This is something I haven't tested myself, and it sounds like you might have already looked into all the options, but I thought I'd throw the idea out there anyway.

In the meantime, I'll keep my fingers crossed that this bug will be fixed soon. Good luck!

Kyle Main

Thanks for your thoughts Claudia, but those settings were not working with our needs.

I'm currently doing deep testing on all settings again.  I'm currently having another similar issue with the Always Resume, while using the FREE Menu navigation. (Not just the Always Resume with Restricted Navigation.)

It was working while doing testing with the WEB publishing feature with the Flash and HTML files, but now that I'm moving on to the next Phase (LMS testing) I have the same issue that I had with the Restricted menu setting.  The issue is with the HTML files that are published.

I'm hoping that when I publish as LMS and click view, that the error will not appear in the actual LMS.  I really hope it could be an issue related to playing it off of a local folder.

Has anyone else had issues with the Always Resume and the Free Menu navigation?

So my work around seems to be broken for all 100% of the many lessons.

I wonder if Javascript code in Storyline could solve these types of issues, if so, would anyone want to make some money to figure out a workaround? 


- Kyle


Claudia K


I just tested this new scenario in our LMS and you're right. If you choose the 'Always Resume' option, the state of the menu is reset even when the navigation is set to 'Free'.

If you resume the course, any slides marked on the menu as previously viewed are reset to their original state. You can obviously still click on any slide on the menu because the navigation is free, but that doesn't take away from the fact that it's a bug. Either way, even if it worked, free navigation is off the table in our case since all our courses require restricted navigation at all times.

I'm really hoping someone will come to our rescue here. 



Kyle Main

Do you know if the variables that have been changed will be remembered?

Does anyone know if the variables within the course will be saved when
returning - in the situation that Claudia just confirmed was an issue with
the Always resume and Free Menu navigation? (And also the Always Resume
and Restricted Navigation)
Is there something I could alter in the published files for 300 storyline
published courses?


- Kyle

*At this point, I'm wondering how this issue was released (I'm wondering
what the process could be for testing the software), I must say, I'm
getting a lot of heat for this issue. My new job is having a hard time
understanding why I kept pushing them to leave Captivate to go to
Storyline. We have the Storyline 360 with this issue.*

*Does this issue happen for anyone with Storyline 2? If so, does anyone
know where we can get a trial to Storyline 2? Does Articulate still offer
that trial?*

Claudia K


I'm so sorry. I can only imagine how stressful this is for you. I'm not able to test it right now, but I'm 99% sure the variables don't get reset. It's just an issue with the menu itself. We use a custom player built with variables and it works well even after resuming the course. I don't know exactly what variables you use in your courses, but I'm guessing the behavior must be the same. 

Now, I know this option is probably very time consuming, but what if you built a custom menu? That way, you can use custom variables to save previously viewed slides and control navigation that way. If you don't have time to build the whole thing out, you could at least have a menu with the main sections so learners can at least jump around among those.

I really hope they fix this soon. I agree with you that it's a huge problem, and I'm surprised more people are not joining in on this discussion. 


Alyssa Gomez

Hi there Kyle,

Thanks so much for letting me know you opened a case. I have passed this forum thread on to Vevette so she can get up to speed with our conversation over the last few days.

So now it seems like we're seeing the same issue with Free Navigation, as well? As Claudia said, it looks like the menu items appear as if they haven't been visited, but fortunately you can click on previous slides with Free Navigation. I'll be sure to add this to the bug report.

Since you asked about variables, I put together two quick samples for you to test. It looks like the variables are retained once the course is resumed, so that's good news.

Also, this does not appear to be an issue in Storyline 2. Give these links a try:

If you'd like to download a trial for Storyline 2, you can do that right here. I know this bug in Storyline 360 has caused major headaches for you, so I am going to advocate for a fix in our next meeting with Quality Assurance. Please let me or Vevette know if you have any other questions or if there is anything else we can do to assist!

Ashley Terwilliger-Pollard

Hi all,

Great news!  We just released another update for Articulate 360, and included a few important fixes that you'll see in the release notes here.  

The item you'll be interested in is how learners couldn't revisit slides they already viewed after resuming an HTML5 course with restricted navigation.

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly. 

Kyle Main

This was exciting news, but this may have caused a new issue or helped us realize an existing issue.

We are using Engage files for the conversation interaction and we have those on slides that are being used as a lightbox.

These will not work with the restricted menu navigation - my guess is that the next button won't officially work just like all other slides that first need the timeline to end.

I first had the progress bar turned on for these slides, then I turned it off and nothing will work. 

Please Help!

This discussion is closed. You can start a new discussion or contact Articulate Support.