A blank trade list can have more than one cause. The run may have failed. The rules may have found no signal. An order may have been blocked or left unfilled. Check which happened before changing the idea.
First, find the last step you can verify
Start with the run-status and error checks. Match the saved rules, data and output to one run. If the result is missing, say it is missing. Do not record zero trades in its place.
This is a review path, not a claim that every app shows these four counts. Use the records your tool provides. If a step is not visible, keep it unknown rather than guessing.
A signal is not a filled trade
A mark on a chart may show that a condition was true. It does not, by itself, show an order or a fill. In TradingView, a Pine indicator can draw marks without placing strategy orders. A strategy must use an order command. See TradingView’s no-orders guide.
Also check what the count means. Open trades and closed trades are separate in Pine. Zero closed trades does not by itself mean no entry occurred. The Pine strategy guide explains orders, fills and trade records. Those details are platform-specific; they do not describe every TradeLab test.
Do not loosen the rules first
Changing parameters until trades appear can hide a setup error and turn one question into another. Freeze the current specification, save the result, and inspect each gate in order.
First confirm that the backtest ran to completion and used the intended market, dates, and timeframe. Then review the six parts of a testable rule.
Six places to look
Read the event counts
If the system exposes signal or condition counts, follow them from broad to narrow. A market filter may pass many bars while a later entry condition passes none. That tells you where the path ended without changing the hypothesis.
If no intermediate counts are available, test each condition alone in a copy of the strategy. Keep the original version unchanged so the diagnostic work has a clean reference.
Timeframe is part of the hypothesis
A daily rule tested on minute bars is not automatically equivalent to a daily test. Indicator values, signal timing, and execution assumptions can all change. Review why timeframe configuration matters before you compare results.
Warm-up can remove the whole sample
Long lookback periods need enough earlier data to become valid. If the test window is short, every eligible bar may occur before the indicator is ready. Extend the history only when that change matches the intended research design.
Some engines reject a test when there are too few bars. TradeLab’s engine source, reviewed November 10, checks for enough input bars and raises an error when that check fails. Do not relabel that error as a successful test with no trades.
Check size and cash before changing the signal
A valid signal can still fail to become a trade. TradingView documents capital and order-size limits among the reasons. Check your tool’s own rules for cash, margin, minimum units and size rounding. Its strategy properties guide describes how these settings work in Pine. Do not raise leverage just to make trades appear.
Hypothetical whole-share example
Suppose a test gives one order a $40 budget. The share price is $60. This example allows whole shares only, with no borrowing or fees. The size is $40 ÷ $60 = 0.67 shares. Rounding down gives zero whole shares. The signal can be valid while the order size is zero.
This is arithmetic, not a TradeLab result or a sizing recommendation. A model that allows fractions can behave differently. Save the limit you found and check the position-sizing guide before designing a separate test.
Follow an order that did not fill
If an order record exists but no fill does, check its type, start time, price, expiry and the available data. A price condition may never have been met after the order became active. Do not count a touched chart price as proof of a fill without the test’s order rules.
When the tool does not expose an order record, keep that gap in your notes. Do not claim an order was rejected, pending or filled without evidence.
Record one of three conclusions
- Run or setup problem. Preserve the error or missing record. Fix a verified setup issue and rerun the same saved rules as a new run.
- Rules are too restrictive for this sample. Keep the result and design a new hypothesis rather than editing the old record.
- No valid opportunity occurred. The strategy may be working as written; test other reserved samples only if that was part of the plan.
Save a short diagnostic note
Record the rule version, market, dates, timeframe, last verified step and missing evidence. Then write one next action. For example: “Signal seen; order record unavailable; inspect the log.” Change one documented issue at a time and keep the first run for comparison.
A zero-trade result becomes useful when it narrows the next question.
Historical testing is hypothetical and does not predict future results. This material is educational, not financial advice or a recommendation.
Platform sources were reviewed November 10, 2026. TradingView examples explain Pine behavior. They do not establish new TradeLab features or public product availability.