Spawn Beacon Occasionally Uses Charge Without Placement

Description of Issue:
When playing as Recon and attempting to place a spawn beacon near a ledge or object where the HUD indicates red (indicating that placement is not possible), repeatedly pressing the placement button (left click) while slightly moving into a position where placement is allowed results in the game consuming the spawn beacon charge without actually placing the beacon.

System Specs:
OS: Microsoft Windows 11 Pro Version 10.0.26100 Build 26100  
Motherboard: ASRock Z390 Phantom Gaming 4  
BIOS Version/Date: American Megatrends Inc. P1.00 2018-08-27  
Processor: Intel Core i5-9600K @ 3.70 GHz (6 cores, 6 threads)  
RAM: 32 GB DDR4 (31.9 GB usable)  
GPU: AMD Radeon RX 6800
Secure Boot: Enabled  
Virtualization: Enabled  

Steps to Reproduce:

1. Play as Recon.
   2. Attempt to place a spawn beacon close to a ledge or object where placement is blocked (red HUD indicator).
   3. Repeatedly press left click (placement button) while moving to a position where placement becomes valid.
   4. Note that the beacon is not placed, but one beacon charge is consumed.

Expected Result:
The beacon should be placed in the valid location when placement is allowed.

Actual Result:
The beacon does not spawn, although the charge is still consumed.