Timing & troubleshooting

Timing (backtest wait)

TradingView doesn’t announce when a backtest has finished, so PineTune watches the metrics and decides when they are stable. You can tune this under Timing in the popup:

Setting	Meaning	Default
Wait after change (ms)	Pause after writing inputs before reading metrics	400
Stable for (ms)	Metrics must stay unchanged this long after a change	1200
No-change release (ms)	If metrics never change, accept them after this long	8000
Per-run timeout (ms)	Maximum wait for a single backtest	60000

• Slow network or heavy strategy → raise Stable for and Per-run timeout.
• Many “timeout” notes → raise Per-run timeout.
• Results look like the previous combination → raise Wait after change.
• Deep Backtesting makes every run much slower; budget accordingly.

Identical metrics for different inputs are legitimate (the inputs may not affect trades), which is why the no-change release exists.

The popup says “Not connected”

• Make sure the active tab is a TradingView chart (/chart/ in the URL).
• Reload the chart tab, then reopen the popup.
• Check the extension is enabled in chrome://extensions.

The strategy isn’t detected

• Make sure a strategy (not just an indicator) is on the chart and visible in the legend.
• Choose it from the dropdown next to the name field, or type its name and click Detect inputs.

Inputs are missing

• Confirm the strategy’s settings dialog opens normally.
• Use the 🔍 button in the parameter section to export an inputs diagnostic and send it to support.

Metrics are empty or wrong

• Let PineTune open the Strategy Tester itself, and avoid switching report pages during a run.
• Use the 📊 button in the results section to export a metrics diagnostic.

Everything is stuck

Click Force reset. If that doesn’t help, reload the TradingView tab and reopen the popup.

Contacting support

Include your Chrome version, TradingView interface language, steps to reproduce and any diagnostic JSON files.