hey,
while I never use int changed, I can imagine that it needs to run while the change is occuring to register it. So it's probably meant to detect changes that are made from another FSM (Set FsmInt etc.). So you must be in the state that has the Int changed action in it.
But just to be on the save side I can propose a technique that works either way.
1) Create a new int variable called "before"
2) then each time you want to check whether the int has changed, do an int compare between your int and "before" . If they are not the same, do whatever needs to be done in that case, then use "set int" at the very end and set "before" to your int. This way when it compares the two again, they are equal.
3) To make this setup not trigger at start, create a new state, make it the start state and use a finished transition to the state that used to be your first state.
In this new state use another "set int" to set "before" to your int.
Did that make sense?