Just wanted to share a new issue and workaround for us when exporting SL course for our LMS (Docebo). The course would launch, but when returning to it we'd get a spinning wheel over SL's resume prompt. The SL menu had "Prompt to resume" checked. When we changed the setting to "Always resume" the issue was solved.
These courses were created by a contractor using settings that we haven't tested in a while. We have not had this issue with in-house generated SL content yet, so it could also be an older software compatibility issue. I'll report back with other findings.
Started happening to all our SLs too. I had to republish with 'always resume,' basically without a prompt, to get it to work. But it just started happening; it worked fine before.
I'm sorry to hear that you're experiencing this issue!
Is this happening with a specific project or multiple files?
Have you tried testing your course in SCORM Cloud? This will help determine if the behavior you're encountering is specific to your LMS.
If you'd like further assistance, we'll be happy to test your file! You can upload it here or privately in a support case. We'll delete it from our systems once troubleshooting is complete.
Multiple files, about 40, basically all our year-end recurrent files we published last week. The majority of them are older and are using the classical player.... hmmm.
5 Replies
Started happening to all our SLs too. I had to republish with 'always resume,' basically without a prompt, to get it to work. But it just started happening; it worked fine before.
Hi Larry,
I'm sorry to hear that you're experiencing this issue!
If you'd like further assistance, we'll be happy to test your file! You can upload it here or privately in a support case. We'll delete it from our systems once troubleshooting is complete.
similar problems:
https://community.articulate.com/discussions/articulate-storyline/launch-issues-in-scorm
https://community.articulate.com/discussions/articulate-storyline/classical-player-impossible-to-resume-a-visited-module
the problem seems to be increasing at the moment
it seems only the classic player is affected
Multiple files, about 40, basically all our year-end recurrent files we published last week. The majority of them are older and are using the classical player.... hmmm.
just tested on scorm cloud
- trainings with classic player (created with storyline 3.63 + 3.68)
- no problems with resume (Firefox 109, Chrome 108)