Octane jump-pad failed jump with correct timing

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number 2080 super
Enter RAM memory size in GB 32gb
What is your gamertag/PSN ID/EA Account name? Photon000
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. Toki123
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)? Any
Which Legends were your squad mates using (if applicable)? Octane
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Any
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Using Octanes jump-pad
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) All the time
How often does the bug occur? Often (50% - 99%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? This is happening constantly, to all of us. No matter the ping. Everything from 20-200ms. Basically, when using the octane jump-pad, a lot of times instead of doing the "superjump" where you hit space right after jumping to reach extra height (not the double jump later), the client will instead get the "jump sound" and do a micro-jump right off the jump pad (basically just a normal jump). For other players, it just looked like he jumped over the jump-pad.
What should be happening instead? The jump-pad should activate, and the client should reach the extra jump-height
Steps: How can we find the bug ourselves? Set down a jump-pad, try to time hitting space for right after the jump-sound is heard. A lot of times this will result in a failed jump

‌

It seems to be a mismatch between what the client sees, and what the server sees. And even though it's timed correctly on the client-side, it doesn't register as such server-side. Please make this timing a client-side thing maybe, to avoid these issues, as it has caused our squad to fail life-saving jumps more times than I can count