3.8 KiB
3.8 KiB
Session: 2026-04-03 - Confluence EA Crisis Analysis & Recovery Plan
Participants
- User: Garfield (garfield@fetcherpay.com)
- AI: Jacob (Algorithmic Trading Partner)
Session Overview
Critical analysis of MultiSignal Confluence EA v1.14 trading halt due to catastrophic account losses. Identified OrdersEA Smart Grid as primary cause of ~$60,000 loss. Created comprehensive diagnostic and recovery plan.
Session Summary
Objective: Diagnose why MultiSignal Confluence EA v1.14 stopped trading for 2 weeks
Key Findings:
- Root Cause: Account equity at 47% (53% drawdown) triggering daily drawdown protection
- Major Loss Source: OrdersEA Smart Grid v3.0/v3.1 caused ~$60,000 loss through high-frequency trading (253 orders on GBPUSD in 24hrs)
- Confluence EA Status: Working correctly but had one bad trade due to ranging market fake signal
- Current State: EA correctly blocked from trading due to risk management protocols
Account Timeline
- March 22, 2026: $106,935.12 balance (+6.94% profit, 71.79% win rate)
- March 24-25: OrdersEA Smart Grid added alongside Confluence EA
- April 2, 2026: Account equity dropped to 47% (~$60,000 loss)
Technical Analysis
Confluence EA v1.14 Features:
- ATR volatility filter
- ADX trend filter
- Dynamic risk management (1-5% per trade)
- 3% daily drawdown limit
- Fixed short signal detection bug (removed restrictive belowPivot check)
Issue: Ranging Market Fake Signal
- EA got caught in whipsaw during ranging market conditions
- This is normal market behavior, not EA malfunction
- Risk management correctly prevented further losses
Current Status
- Daily drawdown protection active - blocking all new trades
- Equity at 47% - below typical minimum thresholds
- EA functioning correctly - protective behavior, not malfunction
- Monitoring plan: Watch for resume next week when daily limits reset
Next Steps
Week of April 7-11, 2026:
- Monday-Tuesday: Monitor for trading resume
- Wednesday: If no trades, begin diagnostic process
- Use diagnostic checklist for systematic troubleshooting
Potential Issues to Check:
- Equity protection too strict (may need >50% to trade)
- Daily drawdown memory persistence (may need EA restart)
- Filters too conservative (ATR/ADX thresholds too high)
- Market conditions unsuitable (continued ranging)
Risk Management Assessment
- Daily drawdown protection: WORKING CORRECTLY
- Equity protection: WORKING CORRECTLY
- Signal quality filters: WORKING CORRECTLY
- Position sizing: APPROPRIATE
Recommendations
Short-term:
- Do NOT modify EA settings yet - let protection systems work
- Monitor market conditions - avoid forcing trades in ranging markets
- Wait for equity recovery or account funding to restore trading capacity
Long-term Enhancements:
- Add breakout confirmation - require 2-3 candles in direction
- Strengthen ranging market detection - avoid trades when ADX < 25
- Time-of-day filters - avoid low-liquidity periods
- Volume confirmation - require above-average volume for breakouts
Files Generated:
confluence_ea_diagnostic.md- Systematic troubleshooting guidetransfer_diagnostic.sh- Script to transfer diagnostic to server2026-04-03-confluence-ea-analysis.md- This session summary
Infrastructure
- Server: 23.120.207.35 (Ubuntu)
- MT5 Account: 104125640 (MetaQuotes-Demo)
- Docker: gmag11/metatrader5_vnc:1.1
- VNC Access: Port 3000
- Git Repository: https://git.fetcherpay.com/garfield/conversation-history.git
Session Conclusion: The Confluence EA is working as designed. The lack of trading is due to proper risk management protecting the account after the Grid EA caused massive losses. Monitor next week for natural resume of trading activity.