Forum Discussion
Rise continue button not enabling after Storyline block completed
- 13 days ago
Hi MarkGray-66105b and MichaelT1,
I have some great news to share! We just released another update for Storyline 360. In Build 3.103.35301.0, we’ve included important fixes. One of the bugs we’ve fixed:
- Completing a Storyline 360 block added to a Rise 360 course didn’t enable the continue block.
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need additional help.
Was this issue resolved? I am having the same issue in one of my Rise courses. Thanks!
Yes, however it seemed to resolve itself. I did not make any changes to the course and one day it just worked. Not a great outcome since I don't know how to fix it if it happens again. Could have been some system updates that were needed. Not sure what the issue was. Good luck with your course. Would love to identify the root cause so I'll keep checking back.
- MarkGray-66105b20 days agoCommunity Member
Hi All, I had the same issue today and tried everything with no success. After trying everything I got my colleague to try and it worked. The difference appears to be that I upgraded my Storyline earlier today and she has not actioned the update yet.
Also I noticed that if you make a block template of the working storyline block this also seems to work in my instance (although I note that normally you would want to change the storyline content)- MichaelT119 days agoCommunity Member
This functionality also stopped working for me after the latest Storyline update (I updated 2025-08-19). Extremely frustrating. Courses I built beforehand work, but trying to add this functionality to my current slate of courses leads to locked Continue buttons that do not open.
I suspect the Storyline devs need to fix this.
- MarkGray-66105b19 days agoCommunity Member
I lodged a ticket and they have indicated they are aware of an issue. The advice in the interim was to revert back to the previous version, which I didn't try as my colleague updated the block for me but may be a temp fix for people?
Pretty big oversight in testing though if there is a bug in the new version.
Related Content
- 5 months ago
- 2 months ago
- 7 months ago