Player pawn or player character will consume input when its triggered. Yes you can change it to not consume, however during development you probably will forget to change it back, and that may cause weird behavior (because you forgot reason for it, or where to change it back).
Better way is to code that (so you see how it works even if you forgot).
For that:
- create dispatcher in player character, lets say Dispatcher_LineTrace
- then in blueprint with line trace: get player character > assign dispatcher (and pick Dispatcher_LineTrace)
- then in blueprint with input (probable player character), call that dispatcher ie. trigger it.
This way everything that needs to be aware of that input gets triggered.