Maybe (happened to me) I wanted to add/change behaviour in C++ and something else was already done in a Blueprint. Took me a while to notice that the event node is consuming the input and the binding functions are not executed in this case.
So you might check your blueprint input actions, if you have some.
