Runtime Error Troubleshooting

There will be some instances where the indicator will encounter a runtime error, which is an error that occurs due to an event that happened when the indicator was being loaded onto the chart. On the rare occasion that runtime errors do occur with our indicators, here's how to fix them.

Quick Triage:

1. Hover your cursor over the red exlamation mark (!) to see the exact message.

2. Switch chart context: set Chart type = Candles/Bars (Standard); try another timeframe; zoom to reduce bars; exit Bar Replay if active.

3. Lighten the indicator via its Inputs: lower lookbacks, disable MTF/multi-symbol features, hide labels/tables, reduce drawings.

4. Reduce global load: remove other heavy indicators.

5. If it still fails, contact our support team and send the exact error shown when hovering over the exclamation mark

The Errors You’ll Most Often See:

1. “Memory limits exceeded.”

   Fix: Turn off heavy features (higher-timeframe internals, large tables/heatmaps). If there’s an option to restrict lookback or date range inside the indicator, use it. Zoom the chart in (fewer bars) and remove other heavy indicators. Read More

2. “The requested historical offset (X) is beyond the historical buffer’s limit (Y).”

   Fix: Zoom the chart in a bit, then re-add the indicator or toggle any setting to force a fresh init. If the indicator has a “lookback” or “history depth” input, reduce it. Read More

3. "Calculation timed out"

   Fix: Turn off heavy features (higher-timeframe internals, large tables/heatmaps). If there’s an option to restrict lookback or date range inside the indicator, use it. Zoom the chart in (fewer bars) and remove other heavy indicators. (Remove the indicator and add it back)