I had the same issue back in May and worked with the support team to solve the problem. Asking the learner to clear their cache isnt an acceptable long term solution for me (and doesndt always work). Please find response below from articulate support team back in May:
A few months ago, we introduced a change to Rise that could cause content to lock up and display a blank page if two things were true:
- You had replaced a Rise course inside your LMS with a different Rise course (or even a duplicated copy of your original Rise course), and...
- A learner attempted to resume a course that had been suspended before replacing the course content.
We won't go into too much detail, but the crux of the problem was a suspend_data incompatibility between the two courses, and the result was a lock-up upon resume.
We’ve fixed this problem, and today one of two things will happen:
- If you replace a Rise course inside your LMS with a revised version of the same Rise course, bookmarking will work as expected. Learners can suspend the course before the course is revised, and those same learners can resume the course after the revision.
- If you replace a Rise course inside your LMS with a different Rise course (or even a duplicated copy of your original Rise course), learners will not be able to resume the course where they suspended it before the revision. In this scenario, learners will return to the beginning of the course, but the content should never lock up.