We receive the attached runtime error message when trying to run a published Storyline 360 file from our LMS. When you select OK, you get the second error message. Can you assist?
I will test using SCORM. I do not think it is our LMS. I think there is a bug in the latest update (I have not updated my system but my user did and they are the ones having the problem).
We went through this problem back September with the completion trigger. Those on the update completion trigger would not work. Those who had not downloaded the latest version of SL 360 the completion trigger worked. To resolve the issue, Articulate had to put out another update that fixed the completion trigger.
3 Replies
To add onto this ticket.
My user published from an updated SL 360 v3.58.26627.0 (runtime error)
I published from an older SL 360 v3.50.24832.0 (NO runtime error)
There may be a bug in the latest update. Can you please check?
thanks
Hi, Veronda.
Thank you for reaching out!
I'd start by uploading the project containing the error to SCORM Cloud and testing it to rule out LMS issues. Check out this step-by-step article!
If it works as expected in SCORM Cloud, I would advise you to reach out to your LMS for more information, as it can be an issue on their end.
If you need help testing, or if you're experiencing the same behavior in SCORM Cloud, please reach out to our support engineers through a case.
Let me know if this works!
I will test using SCORM. I do not think it is our LMS. I think there is a bug in the latest update (I have not updated my system but my user did and they are the ones having the problem).
We went through this problem back September with the completion trigger. Those on the update completion trigger would not work. Those who had not downloaded the latest version of SL 360 the completion trigger worked. To resolve the issue, Articulate had to put out another update that fixed the completion trigger.