Skip to content
Algo Trade Analytics Docs

Knowledge Base & FAQ

Technical resolutions for common reconciliation and ingestion issues.

Symptom: “Signals Not Appearing in Events Log”

Section titled “Symptom: “Signals Not Appearing in Events Log””
  • Diagnosis: Authentication or URL mismatch.
  • Resolution:
    1. Verify the auth_key in your JSON matches the key in Webhook Management.
    2. Ensure your TradingView alert is set to the correct Webhook URL.
    3. Validate your JSON syntax (missing quotes or commas are common).

Symptom: “High Millisecond Latency (>500ms)”

Section titled “Symptom: “High Millisecond Latency (>500ms)””
  • Diagnosis: Heavy payload or TradingView server congestion.
  • Resolution:
    1. Remove unnecessary metadata fields from your alert signal.
    2. Check for high volatility periods; TradingView alert servers may experience delays during market opens.

Symptom: “Invalid Format Error on Upload”

Section titled “Symptom: “Invalid Format Error on Upload””
  • Diagnosis: Non-standard headers or date format.
  • Resolution:
    1. Ensure you are exporting from the Strategy Tester > List of Trades tab.
    2. Timestamps must be in ISO 8601 or standard TradingView format.
    3. Symbols must be clean (e.g., AAPL, not NASDAQ:AAPL).

Symptom: “Low Match Rate in Backtest vs Alerts”

Section titled “Symptom: “Low Match Rate in Backtest vs Alerts””
  • Diagnosis: Logical divergence or repainting.
  • Resolution:
    1. Check for request.security calls with lookahead=on.
    2. Verify if your strategy uses calc_on_order_fills=true, which can behave differently in real-time.
    3. Use Analyze with AI Basic & Pro to identify specific bars where logic diverged.

Symptom: “Symbol Mismatch / No Data Found”

Section titled “Symptom: “Symbol Mismatch / No Data Found””
  • Diagnosis: Ticker format differs between TradingView and Broker.
  • Resolution:
    1. TradingView often uses EXCHANGE:SYMBOL (e.g., NASDAQ:AAPL), while brokers like Alpaca use just AAPL.
    2. Crypto pairs often differ: BTCUSD (TradingView) vs BTC/USD (Alpaca).
    3. Fix: Ensure your webhook ticker field matches the Broker’s expected format.

Symptom: “Missing Fills in Alerts vs Fills” Basic & Pro

Section titled “Symptom: “Missing Fills in Alerts vs Fills” ”
  • Diagnosis: Broker sync or symbol mismatch.
  • Resolution:
    1. Verify your Alpaca account is connected via Integrations.
    2. Ensure the ticker symbol in your webhook signal exactly matches the Alpaca symbol (e.g., BTCUSD vs BTC/USD).
    3. Check if you are looking at the correct account (Live vs. Paper).
  • Webhook Rate Limit: 30 requests per minute per endpoint.
  • Data Retention:
    • Free: 30 days
    • Basic: 6 months
    • Pro: 1 year

If you’ve tried the solutions above and still need assistance: