Forum Discussion

robisorian0's avatar
robisorian0
Community Member
1 hour ago

Continue button is not working while in Review 360

July 29, 2026 

Hello. I am working on a project and I noticed that the continue button is not working. I have 2 topics in one lesson that I needed to separate using the continue button -- locked it to make sure my learners completes the first topic. I went ahead and published for the review 360 and for some odd reason, the continue button remains blocked and I can navigate through both topics without it being unblocked. 

I am sharing an image for reference. 

Take note, this is the 10th version I have published when I got this error. All previous versions are working well. 

Thanks! 

2 Replies

  • Hi,

    I can confirm that I'm seeing what appears to be the same issue.

    From my testing, the behavior seems to be isolated to Review 360. Continue blocks (both locked and unlocked) are not hiding the content that follows, allowing learners to scroll past the Continue block even though it hasn't been completed.

    A few observations that may help narrow it down:

    • The issue does not occur when previewing the course using the Review option inside the Rise editor.
    • The issue also does not appear to affect published LMS packages (at least based on the packages I've tested so far).
    • Continue blocks that were created some time ago may still function correctly in Review 360, but newly created Continue blocks—or blocks modified through Labs → Default Blocks—appear more likely to exhibit the issue.

    Based on my testing, this seems to be a recent regression affecting the Review 360 environment rather than the Continue block functionality itself.

    Hopefully someone from the Articulate team can confirm whether there was a recent update to Review 360 and whether a fix is already in progress. In the meantime, I'd recommend validating behavior in an LMS if possible before making changes to existing Continue blocks.

    Thanks for posting this—it helped confirm that I wasn't seeing an isolated issue.