Trigger on Player is wrong and sort of works but badly

Hi Sam,

The order in which triggers are executed is detailed here but I'm seeing my trigger to jump to the next scene when the timeline ends as a slide trigger, so since you're seeing something different I'd need to take a look at your file to see what else may be different between our examples. 

You would need to add the jump to scene under "Player Triggers".  

Hi Sam,

I am experiencing the same issue, and I have a ticket open.  It seems the "jump to next slide" trigger is converting into a player trigger after saving, closing, and reopening.  It is bothersome because If you open one of the "jump to next slide" player triggers, it will convert back to a slide trigger for as long as you have the project open, but it doesn't save.  The next time you open the project, they will be all player triggers again.  For now, I am converting my "jump to next slide" triggers into "jump to slide x" triggers as they are not affected.  Hopefully they fix it soon because I am having problems saving my file every since.  For me, it happens to all Storyline files, even if I create a new project so I know it isn't slide or file specific.  I also re-installed Storyline 360, and that didn't help either.  I am attaching a test file that when I pull it up, they are all player triggers, and if I click on them and just press "ok", they change to slide triggers.         

Hi Sam and Jamie,

We do have an open issue where a slide trigger has moved to the player trigger. It has been reported happening on files that were upgraded from SL2 to SL360. Is this what you are seeing as well?

Jamie - Can you share your support case where you've reported the above so I can be sure this is all linked together.

I'm adding this thread to our report as we track user impact and so that we can update you here when we can.

Hi Leslie,

My support case is: #01426391.  For me, it happens on all SL360 files on the newest version 3.17.16188.0 (even when creating a new project).  It doesn't seem to be creating any logic errors currently, but I find it very troubling that the triggers don't save as slide triggers unless I change them to jump to a specific slide instead of jump to next slide.  

Thanks so much for sharing your support case Jamie.

I appreciate you letting me know that it's for a new project as well. I see that Robert has filed a report and I've linked the similar one as well as we investigate.

This thread is attached as well so that we can update you when we can.

Hi Everyone,

I am happy to share that the issue where a slide trigger jumps to the next slide and then goes back to the Player triggers is now resolved!

The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline.

If the problem reappears, please let us know! We are happy to help!