Troubleshooting

This guide covers common issues you might encounter during alerts vs fills analysis and how to resolve them.

---

Connection Issues

Alpaca Not Connected

Symptoms:

• “Connect Alpaca” message displayed
• No fill data available
• Feature unavailable warning

Solutions:

1. Navigate to Integrations

   • Go to Account > Integrations
   • Click “Connect Alpaca”
   • Follow OAuth flow

2. Verify connection

   • Check connection status shows “Connected”
   • Verify API keys are valid
   • Test with a simple query

3. Re-authenticate if needed

   • Disconnect existing connection
   • Reconnect with fresh credentials

Note

Paper vs Live: Ensure you’re connecting to the correct Alpaca environment (paper trading vs live) based on where your orders execute.

---

No Data Loading

Symptoms:

• Perpetual loading spinner
• Empty charts and grids
• “No data found” messages

Causes & Solutions:

Cause	Solution
Date range has no trades	Expand or adjust date range
Symbol not traded	Verify correct symbol
API rate limits	Wait and retry
Network issues	Check internet connection

---

Matching Issues

Strategy Uses Pyramid Trading

Symptoms:

• Consistently low match rate despite correct settings
• More fills than expected for the number of alerts
• Multiple fills per alert signal

Cause: Your strategy uses pyramiding (scaling into positions as the market moves favorably).

Not Supported

Pyramid trading is not currently supported by Algo Trade Analytics. Our execution matching expects simple entry/exit sequences:

• ✅ Enter Long → Exit Long
• ✅ Enter Short → Exit Short
• ❌ Adding to winning positions
• ❌ Scaling into trades over multiple orders
• ❌ Partial position exits

Solution:

Configure your TradingView strategy to trade one position at a time:

strategy("My Strategy", pyramiding=1)  // Only allow 1 position at a time

If your live trading requires pyramiding, the execution matching feature won’t accurately reflect your execution quality at this time.

---

Very Low Match Rate

Symptoms:

• Match rate below 80%
• Many “unmatched” alerts
• Many “orphan” fills

Diagnostic Steps:

1. Verify symbol alignment

   • Alert symbol must match fill symbol exactly
   • Check for exchange prefixes (TSLA vs NASDAQ:TSLA)

2. Check time window

   • Default 5 minutes may be too short
   • Try expanding to 15-30 minutes

3. Review alert-fill timestamps

   • Are fills arriving before alerts? (Clock sync issue)
   • Consistent offset? (Timezone issue)

4. Check for duplicate alerts

   • Multiple alerts for same trade?
   • TradingView sending duplicates?

---

All Alerts Marked Unmatched

Symptoms:

• 0% match rate
• Every alert shows as unmatched
• Fills exist but don’t pair

Common causes:

Cause	Solution
Timezone mismatch	Verify UTC timestamps
Symbol format difference	Standardize symbol naming
Wrong data source	Check webhook vs CSV selection
No overlapping period	Align date ranges

---

Fills Without Alerts

Symptoms:

• Multiple “orphan fill” entries
• Fills matched to wrong alerts
• Higher fill count than alert count

Causes:

• Manual trades outside strategy
• Duplicate order execution
• Alert webhook failures
• Different trading source

Solutions:

1. Filter to strategy-related trades only
2. Verify webhook reliability
3. Check TradingView alert history
4. Review Alpaca order history for sources

---

Metric Issues

Unexpectedly High Latency

Symptoms:

• Average latency >5 seconds
• Some trades show minutes of latency
• Inconsistent latency values

Investigation:

1. Check alert timestamps

   • Are alerts arriving late?
   • Webhook processing delays?

2. Check fill timestamps

   • Using correct timestamp field?
   • Broker reporting delays?

3. Review specific outliers

   • A few bad trades skewing average?
   • Market condition (halts, volatility)?

Solutions:

• Improve webhook infrastructure
• Use median instead of mean
• Filter extreme outliers
• Check Alpaca API health

---

Negative Latency Values

Symptoms:

• Fills appearing “before” alerts
• Negative latency in grid
• Impossible timing

Causes:

• Clock synchronization issues
• Timestamp interpretation errors
• Wrong timezone applied

Solutions:

1. Verify system clocks are synced
2. Check timestamp formats (UTC vs local)
3. Review data source configurations

---

Extreme Slippage Values

Symptoms:

• 5% slippage on trades

• Wildly varying slippage
• Unrealistic price differences

Causes:

• Wrong price type comparison (bid vs ask vs last)
• Data errors
• Extreme market events
• Order type mismatch

Solutions:

1. Verify price sources are consistent
2. Check for data quality issues
3. Review market conditions at execution time
4. Confirm order type matches strategy intent

---

Chart Issues

Chart Not Loading

Symptoms:

• Empty chart area
• Perpetual loading
• “Unable to load data” error

Solutions:

1. Check symbol

   • Valid ticker?
   • Supported by Alpaca?

2. Check date range

   • Within available history?
   • Trading days only?

3. Verify Alpaca connection

   • API credentials valid?
   • Data subscription active?

4. Browser issues

   • Clear cache
   • Try different browser
   • Disable extensions

---

Markers Not Appearing

Symptoms:

• Chart loads but no markers
• Only candles visible
• Expected signals missing

Solutions:

1. Zoom/pan to correct area

   • Markers may be outside visible range

2. Check filter settings

   • “Show Only Problems” may hide matched

3. Verify data exists

   • Check grid for entries
   • Confirm date range coverage

---

Live Monitoring Issues

Auto-Refresh Not Working

Symptoms:

• Data not updating
• Same values after interval
• No new trades appearing

Solutions:

1. Verify toggle is on

   • Auto-refresh switch enabled?

2. Check interval

   • Is enough time passing?

3. Browser issues

   • Tab may be throttled (background)
   • Memory issues

4. API limits

   • Too many requests?
   • Try longer interval

---

High Memory Usage

Symptoms:

• Browser becomes slow
• Page unresponsive
• System memory warnings

Causes:

• Long monitoring session
• Large dataset
• Memory leak

Solutions:

1. Refresh page periodically
2. Reduce date range
3. Disable unnecessary data toggles
4. Close other browser tabs

---

Data Issues

Missing Recent Trades

Symptoms:

• Recent trades not appearing
• Delay in data availability
• Gap between trading and visibility

Causes:

• Alpaca API latency
• Webhook processing delay
• Cache not refreshed

Solutions:

1. Manual refresh
2. Wait for next auto-refresh cycle
3. Check Alpaca dashboard directly
4. Verify webhook received

---

Duplicate Entries

Symptoms:

• Same trade appears twice
• Inflated trade counts
• Double-counted metrics

Causes:

• Duplicate webhook delivery
• Multiple alert triggers
• Data import errors

Solutions:

1. Check TradingView alert settings
2. Review webhook deduplication
3. Use unique trade identifiers

---

Getting More Help

If you can’t resolve your issue:

1. Check system status

   • Alpaca API status
   • Platform status page

2. Gather information

   • Screenshot of the issue
   • Date range and symbol
   • Error messages
   • Steps to reproduce

3. Contact support

   • Knowledge Base & FAQ — See “Still Need Help?” section
   • Include gathered information

Tip

Quick diagnostics: Export your comparison data and check it manually. Often, the raw data reveals issues that aren’t obvious in the UI.

---

Related Sections

• Quick Start — Step-by-step guide
• Scope & Matching — Configuration
• Metrics & Analysis — Understanding results
• Alpaca Setup — Broker connection