CRITICAL: TradingView skipping 5-minute trading signals due to 1-minute alert flood
Root Cause:
- 1-minute alerts fire 180 times/hour (60/hr × 3 symbols)
- TradingView has undocumented webhook rate limiting
- High-frequency alerts cause lower-frequency alerts to be dropped
- 2 confirmed incidents of missed 5-minute trading signals
Impact:
- Missed real trading opportunities (revenue loss)
- 5-minute signals are PRIMARY income source
- 1-minute data collection provides ZERO actual value
Analysis Shows 1-Minute Data Unnecessary:
- Smart Entry Timer: Uses signal data (not cache)
- Position Manager: Uses Pyth WebSocket (not cache)
- Quality scoring: Uses signal data (not cache)
- Adaptive trailing: Uses signal ADX (not cache)
- Market data cache updates are vestigial
Solution:
- PAUSE all 1-minute TradingView alerts (SOL/ETH/BTC)
- 83% reduction in webhook load (180/hr → 36/hr)
- 5-minute signals will arrive consistently
- No functionality loss (all systems use signal data or Pyth)
Files Changed:
- docs/1MIN_SIGNAL_OPTIMIZATION.md - Full analysis and implementation guide
- .github/copilot-instructions.md - Added Common Pitfall #1 (webhook flooding)
Next Steps:
1. Pause 3 1-minute alerts in TradingView (immediate)
2. Monitor 5-minute signal delivery for 24 hours
3. Archive BlockedSignal timeframe='1' data (optional cleanup)
See: docs/1MIN_SIGNAL_OPTIMIZATION.md for complete analysis
b7b4707a64