Knowledge Base & FAQ

Use this page to choose the right diagnostic path. A mismatch, missing row, or compiler message is an observation—not a confirmed cause.

Backtest vs Alerts Imports, timezones, unmatched events, chart data, and AI review

Alerts vs Fills Broker connection, alert sources, matching, partial lifecycles, and current-window review

AI Pine Editing Chat modes, context, staged changes, validation, saving, and credits

Algo Lab Data, runtime differences, settings, backtests, and the supervised Agent

A webhook event is missing

1. Open Webhook Management and copy the current endpoint and authentication key instead of retyping them.

2. Compare the TradingView webhook URL and JSON payload with the documented webhook standard. Confirm the body is valid JSON.

3. Check the webhook event log for the same time window. Preserve the HTTP or validation message if the request was rejected.

4. Send one controlled test event before changing the Pine strategy.

Do not post the authentication key in screenshots, support messages, or AI chat.

A CSV will not import

Start with the workflow that owns the file:

• For TradingView Strategy Tester → List of Trades, use the Backtesting Upload guide.
• For alert-history CSV, use Data Scope or Scope & Matching.

Check the actual headers, one raw timestamp, and the chosen timezone. Do not rewrite symbols or timestamps until the importer shows which row or required field failed. Keep an untouched copy of the export for comparison.

A match rate changed

Rerun the same symbol, source, date window, timezone, and tolerances. Then inspect the unmatched rows and compare the source counts before attributing the change to Pine code, a provider, or market conditions.

No universal pass threshold

A match rate, latency, slippage, or engine-difference percentage is not a universal readiness score. Interpret the distribution against the strategy’s intended event semantics and a comparable prior window.

Algo Lab and TradingView disagree

Algo Lab uses an independent Pine-compatible research runtime, not TradingView’s official engine. Compare the same saved source, Pine version, symbol, timeframe, date range, inputs, sizing, commission, slippage, and session settings. Then separate compiler differences from runtime or broker-simulation differences.

Use the Engine vs TradingView guide for the full checklist. TradingView’s Pine Editor and Strategy Tester remain the final evidence for behavior inside TradingView.

The Algo Agent keeps running

Professional

Select Stop to halt the current Agent run at its next safe boundary. Use Ask for a read-only explanation or Research for a bounded research turn that does not apply editor edits. Agent mode can perform multiple supervised steps and may pause for an approval or decision.

If a candidate is staged, review the complete diff. Accepting it changes the editor source; it does not establish profitability or readiness. Validate, save, and rerun the relevant evidence gates.

Market data will not load

• Backtest vs Alerts and Algo Lab may use platform-served IEX stock bars when that fallback is enabled for the page and scope.
• A personal Alpaca connection is required when the fallback is unavailable and for Alpaca fills, portfolio data, and account-specific feeds.
• Confirm the symbol, date window, asset class, and paper/live account before retrying.

See Platform Market Data and Account Integrations.

Still need help?

Open Dashboard → Support and include:

• the route and exact action;
• symbol, timeframe, date window, and data source when relevant;
• the exact error message;
• a minimal reproduction; and
• a redacted screenshot or short recording for visual problems.

Never include passwords, AI-provider keys, webhook authentication keys, authorization headers, or unredacted account data.