SCORM in SCORM

Rise can recognize that a Storyline block was completed (which depends on the tracking used when it is published to Review 360).

However, the block doesn't send any data to Rise—which means it doesn't send the suspend data needed to resume where the user left off. Thus, a Storyline block in Rise always resets when the user returns to the lesson.

Outside of an LMS/LRS, there's nowhere for Storyline to store the suspend/resume data.A Storyline course on the web might sometimes resume, but that's not guaranteed. A lot depends on the user's browser settings and whether they clear their cache between sessions.  

I once saw a post about using JavaScript in a published-for-web Storyline course so it would store its data on the user's local drive. That might work for your situation. 

• Nedim​: Was that one of your amazing JavaScript tips?

JudyNollet​  I’ve demonstrated how to pull quiz data from an embedded Rise course into Storyline, allowing a button state or variable to change based on user success. However, I haven’t worked with this exact scenario, and I don’t believe it’s possible for the reasons you already explained.

ChrisEdwards-92​ The limitation comes from how Rise handles embedded Storyline blocks and SCORM tracking. When a Storyline file is embedded in Rise, it’s treated as a web object (interactive iframe) rather than a SCORM package. This means it doesn’t communicate directly with the LMS so there’s no bookmarking, suspend data, or resume functionality.

In short:
Storyline bookmarking won’t work inside Rise because Rise is the only SCORM “owner,” and the embedded Storyline content isn’t tracked independently.

I wouldn’t go down that route, since the goal is simply to prevent the Storyline block from restarting if the learner has already made some progress. We don’t necessarily need full suspend data to achieve that. Give me a few hours and I’ll come back with an alternative solution.

Nedim​: Thanks (as always) for chiming in with your JavaScript expertise. 👋

ChrisEdwards-92​: Personally, I'm not sure it's worth the effort to try to resume an SL block. 

• If the block only has a short interaction, it wouldn't be that cumbersome for the user to redo the steps—if they ever want to.
• If it's a lot of content/clicks, consider adding a note that warns users it will reset if they leave it partway through. In other words, tell them not to start unless they have the time to finish it.

UPDATE:

Here are the steps I followed:

1. Set the Storyline project to “Always Resume”
2. Publish the project to Web
3. Rename story.html to index.html
4. Zip the published output
5. Add a </> Code block in Rise and upload project 
6. Publish the Rise course to LMS
7. Add the <style> and CSS snippet in index.html, just after the closing </head> tag
   

   <style>
       iframe.block-code {
         --block-html-height: 720px !important;
       }
    </style>
   

   (720px is the Storyline project height—adjust it to match your project.)
   
   
8. Re-zip the project and upload it to your LMS

I uploaded the project to SCORM Cloud and confirmed that the embedded Storyline project resumes as expected.

Try here → https://app.cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=b15e8d80-c099-4bc5-b45b-88773bca44e2 (feel free to use a dummy name and email.)

The key point here is to avoid using Review 360 as the project source and instead embed the Web output. This allows the resume functionality to work correctly. If you don’t rename story.html to index.html, the project can’t be imported and embedded. If you don’t apply the CSS above, the code block won’t take up the full height by default. Once adjusted, it actually looks better than the interactive Storyline block from Review 360.

Just found this too...

https://www.articulatesupport.com/article/Rise-Use-Storyline-Blocks-to-Embed-Storyline-360-Courses#resume

Will embedded Storyline courses resume if learners view them more than once?

Storyline courses in Rise 360 always start over from the beginning when learners revisit them.