If TradingView’s Strategy Tester says “No data,” first check whether a strategy() script is actually submitting simulated orders. A chart signal or indicator arrow is not a trade: the script must reach an order command, the order must be feasible to fill, and the report must have enough results to show the section you opened. The symptom—an entirely empty report, only some blank metrics, or trades that stop appearing—points to different stages of that chain.
Start with the exact “No data” symptom
| What you see | First stage to inspect | Check |
|---|---|---|
| The Strategy Report is absent or asks you to apply a strategy | Strategy is not active | Add or select a strategy() script and confirm it is visible on the chart. TradingView’s Strategies FAQ |
| Overview and Trades both show “No data” | No simulated orders | Check the script declaration, order commands, conditions, runtime errors, and whether the account settings can fund the order. TradingView Help Center |
| Some metrics or visuals say “Not enough data to display” | Sample is too small or the test period is too short | Review the selected history and trade count. TradingView describes 100 trades or more as ideal for a reasonable hypothetical-performance sample; it is not a requirement for a report panel to generate. TradingView’s Strategies FAQ |
| Trades happened earlier but stop on recent bars | Simulated equity or exit logic | Inspect the equity history and whether open positions have exit logic. TradingView’s Strategies FAQ |
| Results look implausible on Heikin Ashi, Renko, or another non-standard chart | Chart prices and fill assumptions | Prefer a standard chart for realistic testing; review the Heikin Ashi standard-OHLC fill option if applicable. TradingView’s Strategies concepts |
Confirm the chart has an active strategy
The Strategy Report is populated by an active Pine Script strategy, not by an indicator or library. Look at the script’s declaration: it must use strategy(). If it uses indicator() or library(), it cannot submit trades to the Strategy Report. Also confirm the strategy is visible and running on the chart rather than merely saved in the editor. TradingView’s Strategies FAQ explains when the report is available.
As an Amazon Associate I earn from qualifying purchases.
Verify that a condition reaches an order command
A plotted arrow, alert, or buy/sell condition does not create a Strategy Tester trade by itself. The script needs an order-placement command such as strategy.entry() or strategy.order(), and its code must actually execute that call. TradingView’s Help Center guidance states that strategies must use strategy.* order commands to simulate orders and display report data, regardless of other signals in the script.
- Find the
strategy.entry(),strategy.order(), or other order-placement call in the code. - Inspect the boolean condition guarding that call. Check whether it becomes true anywhere in the chart’s selected history.
- Use Pine Logs to see whether the relevant code path runs. Plot the condition on the chart if its timing is unclear.
- If the condition never becomes true, investigate its inputs and the selected history before changing its logic. Loosening a condition blindly can change what the strategy tests without identifying the failure.
Look for a runtime error
A runtime error stops a strategy’s calculations, so it cannot continue simulating orders. TradingView says to look for a red exclamation mark beside the script title in the chart pane; click it to view the error. Resolve that issue before interpreting an empty report. The same inspection is recommended in the Strategies FAQ.
#1 Best Overall
Check whether the simulated account can afford the order
An order can be blocked when the strategy’s capital, position size, or margin settings make it infeasible. Check the strategy’s initial capital, base currency, order size and type, and margin settings. Commissions, slippage, limit-order verification, pyramiding, recalculation, and fill behavior can also affect the simulation. Some order commands set their own quantity, overriding the default quantity in Properties. See TradingView’s Strategy properties documentation for the available settings and their effects.
For futures, account for the symbol’s point value
A futures contract’s simulated exposure depends on the chart price multiplied by the symbol’s point value, so the displayed price alone can understate the capital needed. TradingView’s support example uses CME_MINI:ES1! with a point value of 50: a $4,000 chart entry corresponds to a $200,000 contract value in that illustration. The multiplier is specific to that example, not a universal futures value. Check the point value for your symbol, then compare the resulting exposure with the strategy’s order quantity, initial capital, and margin settings. The example appears in the TradingView Help Center.
Distinguish an empty report from an undersized sample
If no order conditions occur in the selected chart history, the strategy has no entries to fill. Expand or change the test range only after confirming that the strategy calculates and its order conditions can trigger. If the report contains some results but individual metrics or visuals say “Not enough data to display,” TradingView attributes that to too few trades or too short a testing period—not necessarily a broken strategy.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →TradingView’s Strategies FAQ calls 100 trades or more ideal for a reasonable sample when assessing hypothetical performance. That is guidance about sample size, not a minimum needed to populate the Strategy Report. Deep Backtesting can examine more available history; the FAQ describes it as available on Premium and higher plans, but check TradingView’s current plan details before relying on that availability.
If trades stop appearing only in recent history
When trades appear earlier but not on later bars, TradingView identifies two possibilities: the strategy may have lost all simulated equity and lack capital to continue, or an open position may have no exit condition. Inspect the equity history. Then check that positions have corresponding strategy.close() or strategy.exit() logic. A position that never closes can appear as an early entry without closed-trade metrics. These are distinct from a script that never generated an order; see the Strategies FAQ.
Separate missing trades from unrealistic chart inputs
A strategy may produce report data while still testing prices that do not represent ordinary market conditions. TradingView warns that non-standard chart types—including Heikin Ashi, Renko, Line Break, Kagi, Point & Figure, and Range—use synthetic prices by default. Its documented recommendation is to run tests on standard chart types. On Heikin Ashi, the standard-OHLC fill option can use actual OHLC values; it does not remove the non-standard time and price characteristics of other chart types. See TradingView’s Strategies concepts.
A Strategy Report reflects simulated, hypothetical performance, not a forecast of future results. Even when the missing stage is fixed, the output depends on the strategy’s code, data, settings, and fill assumptions.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
