Forum Discussion

ShelleySkrab424's avatar
ShelleySkrab424
Community Member
17 days ago

LMS reporting issue

We have recently had an issue when re-publishing a course exam.  We updated one of the questions (text change only).  We left all of our previously set triggers untouched.  When we went to publish the tracking options wouldn't allow us to select Using trigger as its greyed out.  The exam was created on Storyline 360 version from June 2023 (not sure of version number).  Updated publishing was on version 3.92.33225.0

We published to our SumTotal LMS and now the course will not go to fail and the results don't upload.   If a student passes it works fine just. 

Does anyone know why we can't select the Using triggers?  OR any suggestions on what might be going on.  

Thanks

  • Hi ShelleySkrab424!

    Happy to help with this!

    In order to track completion status using Triggers, you need to add at least one Course Completion Trigger to the appropriate slide or layer. You can add as many positive and negative completion triggers as you’d like to a course. However, be sure to add at least one positive completion trigger so learners have the option to complete the course.

    Please let me know if that worked for you!

  • There is triggers on the the next screen for course completion.  Aside from the submit results on the screen shot shown.

    • KellyAuner's avatar
      KellyAuner
      Staff

      Hi ShelleySkrab424!

      Would you be willing to share your .Story file with us so we can take a closer look at how your course is set up? You can upload it here or privately in a support case and we'll delete it from our systems once troubleshooting is complete.

    • officeape's avatar
      officeape
      Community Member

      ShelleySkrab424- We've had a very similar issue when uploading updates to existing courses in SumTotal. The issue (at least for us) seems to be with a recent system update. The "fix" has been to upload an entirely new version of the course (not into the existing LMS course structure) and make sure the "mobile" option is enabled. The issue has to do with the system update using a different internal player, etc., and not passing on the failed status.