Problem: - Close transaction confirmed but Drift state takes 5-10s to propagate - Position Manager returned needsVerification=true to keep monitoring - BUT: Monitoring loop detected position as 'externally closed' EVERY 2 seconds - Each detection called handleExternalClosure() and added P&L to database - Result: .66 actual profit → 73.36 in database (20x compounding) - Logs showed: $112.96 → $117.62 → $122.28 → ... → $173.36 (14+ updates) Root Cause: - Common Pitfall #47 fix introduced needsVerification flag to wait for propagation - But NO flag to prevent external closure detection during wait period - Monitoring loop thought position was 'closed externally' on every cycle - Rate limiting (429 errors) made it worse by extending wait time Fix (closingInProgress flag): 1. Added closingInProgress boolean to ActiveTrade interface 2. Set flag=true when needsVerification returned (close confirmed, waiting) 3. Skip external closure detection entirely while flag=true 4. Timeout after 60s if stuck (abnormal case - allows cleanup) Impact: - Every close with verification delay (most closes) had 10-20x P&L inflation - This is variant of Common Pitfall #27 but during verification, not external closure - Rate limited closes were hit hardest (longer wait = more compounding cycles) Files: - lib/trading/position-manager.ts: Added closingInProgress flag + skip logic Incident: Nov 16, 11:50 CET - SHORT 41.64→40.08 showed 73.36 vs .66 real Documented: Common Pitfall #48
59 KiB
59 KiB