Unfair Hard Breach on Funded Account 414660687 Due to System Error

I am writing this review to warn other traders about a frustrating experience with Goat Funded Trader. ‎On 2026-05-22, my funded account 414660687 was hit with a hard breach and deactivated for allegedly violating the 2% Maximum Loss Per Trade Rule. At the time, I had two open trades on EURNZD H4. The floating loss triggered FLOATING_PNL_BREACHED notifications. ‎Major Issues: ‎According to support and general chat, the first violation of the 2% per trade rule should only be a soft breach (GOAT Guard closes trades + profit split reduced to 50%). Hard breach should only apply on a second violation. This was treated as an immediate hard breach. ‎The breach was labeled FLOATING_PNL_BREACHED, which appears related to overall floating PnL rather than a strict per-trade violation. ‎Clear System Error: The logs show the exact same floating PnL event recorded as two identical separate breaches (same timestamp details, Equity $48,620.16, Balance $50,003.88, Open PnL -$1,379.84). This duplication unfairly escalated a single event into a hard breach. ‎Account Details at Breach: ‎Equity: $48,620.16 ‎Balance: $50,003.88 ‎Floating Loss: -$1,379.84 (within daily drawdown limits) ‎I have attached extensive proof: ‎EURNZD H4 trading chart showing the trades ‎Breach notification emails ‎Account overview & Trading Objectives screenshots ‎Support chat logs with Harry and Onnyechere ‎Help center logs clearly showing the duplicate FLOATING_PNL_BREACHED entries for the identical event ‎This seems to stem from insufficient real-time rule enforcement clarity combined with a system bug. I was trading responsibly and did not intend any violation. Multiple support interactions failed to resolve it, and the account was not reinstated. ‎Traders considering Goat Funded Trader should be extremely cautious with the 2% per trade rule and GOAT Guard system. I hope the firm improves transparency and fixes these system issues. ‎Account ID: 414660687 ‎