Issues with completion/pass tracking of Storyline activities within Rise courses

​@vhung Have you put the course up on Scorm.com and tried it via a mobile browser?  In cases like this, you kinda have to figure out whether it is the course or the LMS that’s the source of the issue. If you can ascertain that it is Go.Learn that’s causing the issue, then I’d log a ticket and see what they say.

Mobile - the bane for many us in the learning mgmt industry. In my younger years when I still had hair and I was still naive, we would put out statements about best compatibility. The problem is that something like 93% of the public is walking around with a mobile device.

The problem with what you are talking about - the nesting experience of a Storyline file to Rise - is that it counts on a few things. You can tighten it up with ​@KMallette mentioned - what we call “test, test, test”. And then test again.

When I ask Google about the problem, here is how it responds back.

When a Storyline 360 course is nested within a Rise 360 course, it may not be correctly marking completion or progress in the LMS. This can happen because Rise 360 only marks Storyline blocks as "completed," not as "passed" or "failed". To ensure proper tracking, you need to configure the Storyline 360 course itself to track completion and publish it to Rise 360 accordingly.
Here's a more detailed breakdown of how to address this issue:
1. Configure Storyline 360 for Proper Tracking:

    Add a "Complete Course" trigger:

On the final slide of your Storyline 360 course, add a trigger that "Completes the course" when the user clicks a button or the timeline starts.
  Choose "Track using complete course trigger"
When publishing your Storyline 360 course, select the "Track using complete course trigger" option. This ensures that the Storyline 360 block is marked as complete in Rise 360.

2. Ensure Correct Rise 360 Settings:

    Set Completion Type for Continue Buttons: In Rise 360, when you add the Storyline block, ensure that the "Continue" button's completion type is set to "Complete the block(s) above the continue block". This requires the learner to complete the Storyline 360 block before proceeding.

3. Troubleshooting SCORM Issues:
If you are still experiencing problems with the SCORM package, check for any random line breaks in the story.html file for the Storyline block. These line breaks can sometimes cause issues with the SCORM package.

Also be aware of Suspend Data Limits:
If your course isn't saving the correct location where the learner stopped, you may be exceeding the suspend data limits. You can find more information about SCORM suspend data limits in the Articulate Community.