Continue button disappearing in completed Rise courses

Renz, unfortunately the Button Stack for all course navigation is not always available, for example at the end of scenario sections and on the quiz results page so using Button Stack option is not always a viable option/workaround.

Following! We have a lesson that uses buttons to create branching scenarios, but the continue buttons disappearing causes major issues because users can't view the lesson more than once. Please make it an option to keep the continue buttons active!!!

Very interested in this thread and any solution Articulate is working on to address the issue. We have multiple branching courses where we use Continue buttons because traditional nav options don't work. However, users often click their browser back button (though there are explicit course instructions not to do so), causing the Continue buttons to disappear and resulting in stuck users. I agree with the general sentiment that a navigation element vanishing is never a good design choice, and I haven't read a good explanation from Articulate why it happens. Is there any movement on the app side to address this truly odd and frustrating functionality? 

I've just spent a day troubleshooting why the Continue button was disappearing when publishing the course in LMS. Once I found out that it goes away upon completion as a default, then I realized that it was when I retested my course in LMS that was the issue.  Now I will remove my completion credit to ensure I can view the course as the learner should see it upon first entry.
I am disappointed to find so many complaints raised about the Continue button over the course of years, and Articulate has not remedied this. Having an option to to keep the button or allow it disappear would be an optimal solution.

Sad to find an issue that we are experiencing which has been pending over three years ago and many more have raised it since and still has not been solved. 

I see this is an older thread BUT the problem persists. I have created detailed engineering courses with a full assessment at the end. Before the users take the assessment, I have used a button to allow them to review the material as many times as needed BECAUSE Rise does not properly restrict navigation if the menu is visible and we did not want an open-book type assessment, so it was logical to use CONTINUE buttons to let the user navigate. Unfortunately, this behaviour has now come as a nasty surprise on the cusp of the course being launched. Luckily, I caught in during final staging, but I will now need to find another workaround. Very disappointing. 

Can ANY Articulate staff chime in? This lack of an option to keep the Continue button visible has been an issue for FOUR YEARS.

The excuse given for this ridiculous Continue button functionality was basically, "You are not supposed to design your courses that way!" Just terrible.

Any update on this please?

I, like many others in this thread seem to have discovered this the hard way after revisiting my content prior to a learning refresher rollout.

So now realising my learners will not have the same user experience I had intended when using 'Continue' buttons to provide breaks to flow in my microlearning content. Now they will just have one big scrollable page. 

4 years on this must have made its way up the priority list by now? 

I would also like to weigh in and say that the ability to turn off this function would be super helpful. The intention here is very un-intuitive. I don't understand a case where this would be the desired behavior. In my case the lesson numbering didn't work for the clients course structure so I had to turn it off, but it still shows in the default navigation buttons so I turned them off as well, then went through and added continue blocks throughout the entire course. Now the client is complaining that the blocks disappear. The solution I am finding online is to use a button block instead but that means I need to go through every page of the course and manually replace the continue block that seems specifically designed for this type of case. This is very frustrating.

I also just realized that the button blocks have a totally different design. I am forced to have a little button off the the right instead of the large, full width navigation button we had before.