Since Storyline 360 Jan 21 2020 update layers with True/False variables and Change settings are being jumped.

I'm having a very similar issue, also. Same as you, except that I'm using number variables (rather than true/false) with triggers, to show layers. They aren't working either. When triggered, jumps straight to the highest/last number variable value setting, skipping over the intervening ones.

Have you heard anything from Articulate Support yet?

I've also now submitted a ticket too...

Hi Ron, 

Thanks for contacting the support team and working with Ronaziel on this issue.

Hi Alexandra and welcome to E-Learning Heroes :)

To answer your question, it looks like Ron is still working with our team, so thank you for contacting them as well to share what you are running into and I can see that you're currently working with Peter.

Hey, Alexandra.

My supervisor tried a numeric variable variant when we started having troubles and yes, his had these similar issues with his version of our module.

I'm sorry to note that support thinks there is no issue here -- that the triggers are merely out of order. As they are conditional true/false issues in my module I can't imagine that would change the issue. Both my supervisor and I have backloaded the previous version into computers until the dust settles on this, because we can't have a technique we use all the time suddenly not work in any of our modules.

Seems I've got the same kind of problem.

I updated a SL2 file where I've got 4 boolean variables that lock navigation once 4 sections (scenes) have been viewed (a trigger sets each variable to True when a scene is viewed.

Those trigger-set variables are ignored unless I set them to True by default! 

Hi Pierre,

Thanks for letting us know that you are running into an issue as well.

With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Hi Leslie,

I'm having a similar issue. Unless it's user error??? I'm trying to set the Next button to hidden when the timeline starts, and then change to normal once the slide layer is viewed and the user is brought back to the base layer. I'm using a T/F variable. I've included a sample file for review. Please let me know if this is user error or a technical issue. Thanks!

Hi Lindsey,

I think you have to set state change on "variable changes" instead of "timeline start" because timeline won't start again as you stay on the same slide :

Pierre

Hi Pierre,

Thank you!!! That was an easy fix :)

Have to agree with the posts here. After updates, triggers are completely ignored while they worked perfectly normal before. 

I submitted a ticket for the issue but thought I'd voice my opinion here too in agreement with the above comments.

Hello, Wyeth!

Thanks for writing in and for opening a support case! I'd love to share Johnrey's findings publicly in case others have the same experience:

It looks like the trigger won't work when the variable value is between 6-2. That's because the starting value was greater than the ending value.

For this trigger to work, the values must be in the right order, wherein the first value or the starting value should be the lowest number and the ending value being the highest number. For the trigger, change the values 6 and 2 to "between 2 and 6" instead.

More details here: Storyline: Between Operator for Trigger Conditions Includes Your Starting and Ending Values

Let us know if you need anything else!