Runtime Error Troubleshooting

TradingView indicators can occasionally produce runtime errors. This page covers the most common issues and how to resolve them.

What Is a Runtime Error?

A runtime error occurs when an indicator fails to execute on a chart. TradingView displays a red exclamation mark or error banner on the indicator when this happens. The indicator will stop rendering signals and overlays until the error is resolved.

Common Runtime Errors

"Study Error" or "Script Error"

This is the most generic TradingView error. Common causes:

• Insufficient historical data — The symbol or timeframe does not have enough bars for the indicator's calculations
• Unsupported symbol type — Some exotic instruments or spreads may not provide the data fields the indicator requires

Fix: Switch to a different timeframe or a more liquid symbol. Most major crypto, stock, and forex pairs work without issues.

"Loop Takes Too Long"

TradingView imposes execution time limits on Pine Script indicators. This error appears when calculations exceed the allowed duration.

Fix:

1. Reduce the number of active modules in the indicator settings (disable components you are not using)
2. Use a higher timeframe — lower timeframes have more bars to process, increasing execution time
3. Avoid loading the indicator on illiquid symbols with irregular data

"Array/Memory Limit Exceeded"

Pine Script has memory constraints. Indicators that track many data points (such as multi-symbol screeners) can hit these limits.

Fix:

1. Reduce the number of symbols in the screener configuration
2. Lower the lookback period in the indicator settings
3. Switch to a higher timeframe to reduce the number of bars processed

"Cannot Call Function — Too Many Calls"

TradingView limits how many times certain functions can be called per script execution.

Fix: Disable unused modules or reduce the screener symbol count. This frees up function calls for the components you actually need.

Indicator Loads but Shows No Data

This is not technically a runtime error, but a common issue:

• Check the timeframe — Some indicator modes are designed for specific timeframes
• Check the symbol — Verify that the symbol has sufficient trading history
• Check the settings — Ensure the relevant signal types are toggled on in the settings panel

General Troubleshooting Steps

If you encounter a runtime error that is not listed above, try these steps in order:

1. Refresh the page — Sometimes TradingView's script engine needs a clean reload
2. Remove and re-add the indicator — Delete the indicator from your chart and add it again from the Invite-only scripts tab
3. Reset to default settings — In the indicator settings, click the reset button to restore defaults
4. Try a different symbol or timeframe — This helps isolate whether the issue is data-related
5. Clear browser cache — Cached data can occasionally cause conflicts with updated indicator versions
6. Check TradingView status — Visit TradingView Status to see if there are platform-wide issues

TradingView Plan Limitations

Some runtime issues are caused by TradingView plan restrictions rather than indicator bugs:

If you are on the free plan and try to add more than 2 indicators, TradingView will block the addition. Upgrade your TradingView plan if you need more indicator slots.