I also managed to reproduce it on 5.5.4
One way that I worked around this issue was to set a trigger pressed on the input, and in the EnhancedInputAction event, I used Triggered instead of Started.
pressed
