Forum Discussion

cbcasas's avatar
cbcasas
Community Member
4 months ago

Continue buttons not progressing as expected

This must have happened overnight but when a Continue button is placed at the end of a module, it doesn't automatically progress to the next module. This now occurs with all courses I am actively and previously worked on, essentially breaking navigation. Is this a new feature or bug? 

31 Replies

  • Good morning! It appears that the Continue button is functioning today! No official response from Articulate, so I imagine it was a bug created by the numerous changes they are currently making.

  • I can advise this has been resolved, Articulate have fixed the bug and fix released. Refresh page and the continue button is will work as expected.

  • The issue seems to have been resolved, but only after creating a copy of the original course.

    With the original course:

    • Preview mode: Continue button works as expected, directing to the next lesson.
    • Republishing to Review360: Issue persists when creating a new version or overwriting an existing one.


    Workaround: creating a new copy of the course restores normal functionality in Review360 for both new and overwritten versions.

  • I submitted a ticket for this same issue today before I saw this thread. I also hope this is a bug and that there can be some transparency on the issue soon. We uploaded about 10 SCORM files yesterday, and our reviewers today all noted this behavior. We urgently need help, as we're trying to release two new learning programs tomorrow. 

    • MelanieKing-f58's avatar
      MelanieKing-f58
      Community Member

      CarinDOliva-625​ - i got this reply this morning - you probably just need to republish again and the issue should be resolved. 

      Good news! We’ve fixed the issue in Rise 360 where the Continue block/button failed to move to the next lesson.

      Here’s what you can do to ensure the fix applies:

    • EricSantos's avatar
      EricSantos
      Staff

      Hi SanduniFernando,

      Thanks for checking in on this. I completely understand why this would raise a flag, especially since there was a similar issue before.

      I did some testing on my end and wasn’t able to reproduce the behavior, and we’re not seeing this reported as a widespread issue at the moment. If you’re noticing this in a specific course, it may be isolated to that setup or output.

      As a quick step, try clearing your browser cache, then refresh or republish the course to see if that resolves it. If the issue continues, please connect with our support team by creating a case so we can take a closer look.