Forum Discussion
Problems with copied & changed trigger with OR conditions
Thanks for your replies. I only use JavaScript when I can't solve something with triggers, and I use triggers for the most complicated calculations and decisions. So that's quite different from how you do it :-)
Nevertheless, I think that copy/pasting a very simple trigger and modifying it should not result in a corrupt trigger that does not do what it is supposed to do.
Maybe Storyline staff could react on this post? Is there any idea when this bug is going to be solved?
Hi UPlearning,
Thanks for sharing the additional context and details around this behavior. I can understand why this would be frustrating, especially when a copied trigger ends up behaving differently after only minor condition changes.
I did some testing on my end and wasn’t able to reproduce the issue in a brand-new Storyline file. However, I can see the behavior you’re describing in the example you shared, so I’d like to follow up with our engineering team to take a closer look.
You mentioned this was previously reported and reproducible around 3 years ago. If you still have the link to that older discussion or report, could you share it here? That would be really helpful so I can reference the earlier findings and connect the investigations together more easily.