Skip to content
Algo Trade Analytics Docs

Troubleshooting

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


Symptoms:

  • “Invalid CSV format” error
  • “Missing required columns” error
  • File upload fails silently

Solutions:

  1. Verify file format

    • Open the file in a text editor
    • Ensure it’s comma-separated (not semicolon or tab)
    • Check that the first row contains headers
  2. Check required columns

    • Must have: Trade #, Type, Signal, Date/Time, Price
    • Column names should match TradingView’s default export
  3. Fix encoding issues

    • Save as UTF-8 encoding
    • Remove any special characters in headers
  4. Try paste method

    • Open CSV in Excel/Sheets
    • Copy all cells
    • Paste into the upload zone

Symptoms:

  • Upload succeeds but shows “0 trades loaded”
  • Backtest step doesn’t complete

Causes & Solutions:

CauseSolution
Empty CSV fileRe-export with trades visible in Strategy Tester
Date filter activeCheck TradingView chart date range
Strategy not runningEnsure strategy is added to chart
Export from wrong tabUse “List of Trades” tab, not “Overview”

Symptoms:

  • Webhooks selected but “0 signals” displayed
  • Alert data source appears empty

Solutions:

  1. Expand date range — Your alerts might be outside the selected window

  2. Check webhook configuration

    • Navigate to Webhook Settings
    • Verify your endpoint URL is active
    • Check recent event history
  3. Verify TradingView alerts

    • Open TradingView Alert Manager
    • Confirm alerts are set to your webhook URL
    • Check alert history for recent triggers
  4. Switch to CSV — Use CSV import as a temporary workaround


Symptoms:

  • Consistently low match rate despite correct settings
  • More entries in backtest than expected
  • Multiple entries before a single exit

Cause: Your strategy uses pyramiding (adding to positions as the market moves favorably).

Solution:

// Change your strategy declaration to:
strategy("My Strategy", pyramiding=1) // Only allow 1 position at a time

If your strategy requires pyramiding, you’ll need to modify it for compatibility or wait for future platform updates.


Symptoms:

  • Match rate below 50%
  • Many “missed alerts” despite having alert data

Diagnostic Steps:

  1. Check timezone alignment

    • Compare a specific backtest trade time with its expected alert
    • Is there a consistent offset (e.g., always 5 hours different)?
    • Adjust timezone offset in Backtesting Upload step
  2. Verify symbol consistency

    • Backtest symbol must match alert symbol exactly
    • Check for exchange prefixes (NASDAQ:AAPL vs AAPL)
  3. Review tolerance settings

    • Time tolerance may be too tight
    • Price tolerance may be too tight
    • Start with relaxed settings (15 min, 5%) and tighten gradually
  4. Check date range overlap

    • Ensure your selected dates cover both backtest AND alert data
    • Some alerts may be outside your analysis window

Symptoms:

  • Signals would match if shifted by X minutes/hours
  • Consistent offset across all trades

Cause: Timezone misconfiguration

Solution:

  1. Calculate the exact offset (e.g., 3 hours)
  2. Go to Backtesting Upload step
  3. Adjust timezone offset slider
  4. Re-run analysis

Symptoms:

  • Entry signals show high match rate
  • Exit signals show many misses

Causes & Solutions:

CauseSolution
Alert only on entriesAdd TradingView alerts for exit signals
Different signal namesEnsure exit alerts use consistent naming
Exit logic differsCheck if strategy exits differently in real-time

Symptoms:

  • Matches found but with high price drift
  • Price tolerance warnings

Causes & Solutions:

CauseSolution
Volatile marketIncrease price tolerance
Different price typesCheck if using close vs. last price
Data feed differencesAccept as expected variance
SlippageNormal for market orders

Cause: Not all workflow steps are complete.

Check each step:

  • Data Scope: Date range selected AND data source chosen
  • Strategy Properties: Name AND symbol entered
  • Backtesting Results: CSV uploaded with trades
  • Analysis Configuration: Tolerances set (default is OK)

Symptoms:

  • Spinner runs for more than 30 seconds
  • Page becomes unresponsive

Solutions:

  1. Reduce data size

    • Narrow your date range
    • Filter to specific signals
  2. Refresh and retry

    • Browser may need refresh
    • Data may be cached on retry
  3. Check browser performance

    • Close other tabs
    • Clear browser cache

Symptoms:

  • Changed settings but results look the same
  • Previous analysis still showing

Solutions:

  1. Ensure “Run Analysis” was clicked — Not just “Save”

  2. Clear snapshot context

    • If viewing a saved snapshot, switch to “Live data”
    • Re-run analysis on fresh data
  3. Hard refresh the page — Ctrl+Shift+R / Cmd+Shift+R


Symptoms:

  • Chart area shows loading spinner indefinitely
  • “No data available” message

Causes & Solutions:

CauseSolution
Alpaca not connectedCheck broker integration
Invalid symbolVerify symbol format
Weekend/holidayNo data for non-trading days
Network issueCheck internet connection

Symptoms:

  • Chart loads but no signal markers visible
  • Expected triangles/circles missing

Solutions:

  1. Check date range — Zoom/pan to where signals should be

  2. Verify data exists

    • Check trade count in Backtesting Results
    • Check signal count in Data Scope
  3. Adjust timeframe — Some timeframes may not show markers well


Symptoms:

  • Button is grayed out
  • Hover shows error message

Solutions by error message:

MessageSolution
”Run analysis first”Complete the comparison analysis
”Configure AI in Account Settings”Set up AI credentials
”Upgrade to Basic”Free plan doesn’t include AI
”No credits remaining”Purchase more credits

Symptoms:

  • AI starts but returns error
  • “Failed to generate insights” message

Solutions:

  1. Retry the request — Transient errors are common

  2. Reduce data size — Very large analyses may timeout

  3. Check account status — Verify credits and subscription

  4. Try different model — Switch to faster model in Account Settings


Symptoms:

  • Save button disabled or errors on click
  • “Snapshot limit reached” message

Solutions:

  1. Check snapshot count

    • Free: Limited to 1-2 snapshots
    • Basic: Up to 5 snapshots
    • Pro: Up to 20 snapshots
  2. Delete old snapshots

    • Use the snapshot dropdown
    • Click delete on unused snapshots
  3. Run analysis first

    • Cannot save without results

Symptoms:

  • Selected snapshot but nothing happens
  • Loading spinner indefinitely

Solutions:

  1. Check network — Snapshot fetch requires API call

  2. Refresh the page — Stale state may cause issues

  3. Delete and recreate — Corrupted snapshot data


If you can’t resolve your issue:

  1. Check Knowledge BaseKnowledge Base

  2. Contact SupportKnowledge Base & FAQ — See “Still Need Help?” section

    • Include your analysis details
    • Attach CSV files if relevant
    • Describe steps to reproduce
  3. Export your data

    • Download your backtest CSV
    • Export comparison results
    • Take screenshots of the issue