Forum Discussion
Blocking Course Progress on LMS Communication Loss
Hi everyone,
we're working on a SCORM course developed in Articulate Storyline, and we’re trying to implement a specific client requirement — but we’re stuck.
The requirement:
If the communication between the course and the LMS is interrupted, the course should:
- block any further progress, and
- display the following message:
Warning! Communication with the platform has been interrupted.
Please close the course and reopen it after checking your network connection.
What we've tried:
Normally, we manage this kind of behavior directly through LMS settings, but in this case, the client insists that the logic must be handled within the SCORM itself.
We've tried everything we could think of to detect communication loss and trigger this behavior from within Storyline — but nothing has worked so far. At this point, we honestly don’t know what else to try.
Has anyone faced a similar situation?
Is there any workaround or JS-based solution that could help us detect LMS connection issues and respond accordingly from within the SCORM?
Any help would be truly appreciated!
Thanks so much in advance,
Andrea
1 Reply
- JoeFrancisCommunity Member
I did, many, many years ago when I was using AICC over much more fragile networking. I set the course to "ping" the LMS at regular intervals and then used back-end logic to allow the learner to proceed if the LMS was still "there." The way I did it was by retrieving the current completion status and then sending that same status back to the LMS. If the LMS didn't respond, the course would display a similar error message.
If the built-in SCORM function lmsAPI.GetStatus is still available, you could do something similar in Storyline. If the LMS responds with anything other than what is expected (last time I checked several years ago, the responses were as listed below; Storyline at the time was transposing the letter response from the LMS to a number), you could then display the error message.
- Passed
- Completed
- Failed
- Incomplete
- Browsed
- Not Attempted
Related Content
- 5 months ago
- 3 months ago
- 4 months ago
- 10 months ago