Triggers moving randomly

Dec 27, 2018

Hi all, 

I am using Storyline 3 and I am trying to replicate a complex (for me) trigger system to have a quiz that repeats and reviews only the wrong answers. I found the solution on this forum. 

I have got it working reasonably well. But when I create the triggers on a slide and get them into the correct order then move away from the scene. When I return to the scene, one of the triggers keeps moving. It is a 'jump to next slide if...' trigger which I want first in the trigger list as a 'slide trigger'. However, it keeps moving to second trigger under the 'player triggers'. The player triggers are always at the bottom of the list. 

This is having an impact on logic of the triggers. Anyone experienced this or know how to stop it?

6 Replies
Ashley Terwilliger-Pollard

Hi Marcus,

What's the rest of the trigger - Jump to next slide if...? Triggers will organize themselves based on a slide item or a player item, and they'll execute as described here.  

It would also help to take a look at your .story file if you're still stuck. Can you share a copy of it with me here? If you'd prefer to share privately, you can always send to our Support Team here. 

Marcus Haddon

Hi Ashley

Apologies for the late reply. Happy New Year. I managed to publish the work but had to adjust the trigger on 30 odd slides before publishing it each time.

The trigger is Jump to slide... when timeline started if... and...

I want it as a slide trigger and that where i add it. but often it moves to being a player trigger. And not consistently on all question slides.

I'll probably pop it into the support team but if you have any further ideas please let me know.

Ashley Terwilliger-Pollard

Hi Marcus, and Happy New Year to you too! 

I'm glad you were able to publish it, and get it working as needed. How did you end up adjusting the trigger to have this work - I think that's the insight I'd need to understand what was happening. 

Were all triggers set up with the additional if/and statements? 

For example, although it sounds like a slide trigger (relying on the slide timeline, or variables/state changes) it could become a player trigger if controlling a player button such as the next, submit, etc. 

I didn't see a case for you yet, but if you do submit one let me know and I'd love to follow along. 

Marcus Haddon

Hi Ashley, 

It was on my list yesterday, now pushed to today so we'll see how that goes. All the triggers that moved were in a similar format. the if/and elements were referencing Variables that changed based on actions on other slides. 

I got it working by moving all the triggers to the right place and publishing before closing it down. I found that once i save and closed the file and opened it again most of them would have moved, This method obviously becomes repetitive when you have reviews and small changes to make.  

Ashley Terwilliger-Pollard

Hi Marcus, 

Something you said struck a chord, so I did a bit more digging! 

I found two similar reports of the trigger moving, and in one of those instances, it occurs when the file has been upgraded from Storyline 2 to Storyline 3/360 and only on a quiz slide which also had a submit trigger.

The other report indicated the trigger would still work as expected unless there was a variable attached to it. That seems to match your setup and what you've run into. 

You already identified one of the workarounds, to save and publish at that point before closing. The other strategy, if it's a jump to next slide trigger when the timeline ends, use the direct slide/number instead of simple next slide. 

I'll also include your discussion in that report and will keep you posted!

Vincent Scoma

Hi Marcus,

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!

This discussion is closed. You can start a new discussion or contact Articulate Support.