It's not a bug, you just have a dependency on the order of events. Some triggers fire at different times, and the gamepad trigger can run just before "every tick". In this case dt is still a nonzero value (because dt doesn't change during ticks), and the "set timescale" action in the "every tick" event will override the previous one.