Forum Discussion
You are offline. Trying to reconnect... message when viewing course on LMS
Hi there. We are encountering circumstances where folks are viewing SL courses on our LMS and get this message. If they close out of the course and relaunch it doesn't seem to be tracking their pr...
Hi, everyone!
I have some great news to share. We just released another update for Storyline 360. In Update 76, we’ve included important fixes and new features!
One enhancement we’ve included:
The lost connectivity alert is now optional. Turn it on in the player properties.
To take advantage of this update, launch the Articulate 360 desktop app on your computer, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
The issue has not been resolved. I was disappointed to see another update go out and nothing done about this. As stated above it is happening on all devices, browsers, connections, platforms and to over 30 courses among multiple development departments. I am working with a support case, but it is not helpful because it is not something that can be replicated. It happens randomly multiple times a day to learners taking our courses. And as I see above it is happening to many people. So looking at our Articulate files is not going to help. We are developing our courses in the same manner we were before this feature was added. It is clearly the feature that was added not working correctly. Even if it is fixed at this point it will require us to republish over 30 courses. Is someone actually looking at correcting this feature? Are there any plans to remove it? It is not working as intended.
the error has nothing to do with LMS - you can produce this error easy without an LMS
- publish to Web
- go to publish folder "mobil" and rename one image (which is on base layer of the first slide)
- start the course on a webserver
- so only one harmless 404 error should appear, but the training should start
- BUT storyline starts with the "lost connection" message and tries to load every 0.5 sec the non existing image for ever
that the total wrong methode to handle a 404 or other internet errors !!!!
if data cannot be delivered - because e.g. a webserver or a proxy server cannot handle data at this moment, you NEVER make such a short and fixed time interval for endless retry. This will make an perhaps existing small problem much worse.Do you suggest we revert back to previous versions of Storyline, before the update?
