Forum Discussion
Continue button not unlocking after the Process Block - published SCORM file
07/31/2026
Hi,
There is another error in Rise. This time, the error with the Process block before a locked continue button.
It may seem to work in both the preview and the review 360 but this function is not working when it is already published as SCORM and uploaded in the LMS. I have to refresh the web in order for the continue button to unlock.
Please help investigate.
5 Replies
- Kyle_EricksonCommunity Member
Hi @robisorian0,
Just adding to SamHill's suggestions: since it works in Preview and Review 360 but breaks once published, the SCORM wrapper is the more likely culprit than the block itself. Rise changed its LMS exporter in early July and a few unlock and tracking quirks have surfaced since. Two quick checks before raising a case: were you on the new default export or the Legacy option when you published, and does the same zip behave the same way in SCORM Cloud's free tester? If Legacy fixes it, that's useful evidence to hand Articulate support.
- robisorian0Community Member
hi Kyle_Erickson - thanks! I extracted SCORM using the Legacy and the default export and both showed the same error. I raised a ticket last Friday and eventually got a fix over the weekend.
- Kyle_EricksonCommunity Member
Good outcome, and useful to learn that both exports behaved the same. I think that points at Rise itself rather than the SCORM wrapper this time. Curious what the fix ended up being if support shared any detail, since a few of the Jul-post-exporter-change threads sound similar.
- SamHillSuper Hero
Hi robisorian0 I'm sure you have tried publishing the content again.
You could also try deleting and adding the Continue button again.
If this still does not work, I would recommend taking this directly to Articulate support and raising a case with them
https://access.articulate.com/support/contact/360-teams
- robisorian0Community Member
hi SamHill - thanks. I did those basic troubleshooting and it did not resolve the issue so I logged a ticket to the support team last Friday and it got resolved over the weekend.