Hi,
It's likely because you have a local variable named exactly as the global variable and PlayMaker will use the local one on new instances. This is a known issue and is not likely to change in the near future, so make sure your global variables do not conflict with your template local variables
Also, inside template, it's likely highly preferrable to not user global variables, and instead create a variable that you expose in the inspector so that the run fsm sees it and you feed your global variable value viz this intermediate template variable.
Bye,
Jean