> For the complete documentation index, see [llms.txt](https://docs.iblvautomated.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iblvautomated.com/getting-started/faq.md).

# FAQ

Find answers to common questions about setup, requirements, and how IBLV Automated tools work.

{% hint style="success" %}
Check out the rest of the help centre if you run into anything, or use the **Ask** button to chat with the assistant.
{% endhint %}

## NinjaTrader Products

<details>

<summary><strong>How do I know if I have full level 2 market data?</strong></summary>

Learn how to verify whether you have Level I data, Level II data, or full market depth inside NinjaTrader [HERE](/lms-ninjatrader-set-up-guide/connecting-your-level-2-data/how-to-check-if-you-have-level-ii-data-and-full-market-depth.md)

</details>

<details>

<summary><strong>Why can't I see levels on my chart?</strong></summary>

**Problem:**\
No liquidity levels appear on the chart

**Causes & Fixes:**

* **Level 2 data not connected**\
  Fix: Connect your data provider under Connections.
* **Using limited data (Top of Book)**\
  Fix: Make sure you have full CME Level 2 market depth.
* **Using Other Account Connections**

  If you have multiple connections, **the Apex Rithmic connection should connect first**. LMS uses **the first active connection for data**.

  Fix:

  * Connect **My Rithmic for NinjaTrader Brokerage** first
  * You can then connect other accounts after that
  * LMS will pull its Level 2 data from that first active feed
* **Market is inactive or outside session time**\
  Fix: Check your session settings and current market conditions.

</details>

<details>

<summary><strong>Does it matter which level 2 data I purchase?</strong></summary>

**Yes. Choosing the correct Level II data provider is one of the most important parts of setting up LMS.**

LMS is designed to analyze **full Level II market depth**. If your data provider offers limited market depth, LMS will detect fewer liquidity levels and may not provide the intended experience.

#### Our Official Recommendation

We **officially recommend using an Apex Trader Funding account with Rithmic Level II Market Depth.**

This is the configuration we have thoroughly tested and actively support. It consistently provides the full market depth required for LMS to function as designed.

#### Data Providers We Do Not Recommend

At this time, we **do not recommend** using:

* NinjaTrader Brokerage Level II
* Tradovate Level II
* Other prop firms or data providers that have not been tested by our team

While some of these providers may offer Level II data, we cannot verify the amount of market depth they provide or guarantee that LMS will perform as intended.

#### Other Tested Options

Some members of our community have also reported success using **Bulenox accounts with Rithmic Level II Market Depth**. However, this configuration has not been officially tested or supported by IBLV Automated.

For that reason, **Apex Trader Funding with Rithmic remains our only official recommendation.**

If you're unsure which data subscription to purchase, we recommend contacting our support team before subscribing so we can help ensure you choose a compatible setup.

</details>

## TradingView Products

### Errors

<details>

<summary><strong>Why am I getting a "Memory limits exceeded" error?</strong></summary>

This error occurs when TradingView's memory cap is hit by the indicator's data requests. The most common cause is running the indicator on a sub-1 minute timeframe (15s, 30s, etc.) with multiple heavy features enabled simultaneously — such as Supply & Demand Zones across many timeframes, MTF Confluence, Heat Zones, and the Watchlist Scanner all active at once. Each feature requests additional data that compounds the memory load.

To resolve this: disable features you aren't actively using (the Scanner and S\&D Zone timeframes are the heaviest), or move to a 1-minute or higher timeframe. If you need to use sub-1m charts, we recommend turning off S\&D Zones and the Scanner while on those timeframes.

</details>

<details>

<summary><strong>Why am I getting a "Loop takes too long" or "Runtime error: Script has run for too long" error?</strong></summary>

This is TradingView's per-bar execution budget being exceeded. It typically appears on 1-hour or higher timeframes where each chart bar contains a large amount of sub-bar history, or when a high number of levels and zones are being evaluated simultaneously.\
\
First, try removing the indicator and adding it back. If it doesn't work, try the steps below.&#x20;

To resolve this: reduce the Max Active Levels count, disable the Watchlist Scanner, or turn off S\&D Zone timeframes you don't need. If it occurs only on specific high timeframes, switching the Volatility Timeframe (Risk Calculator) away from a very high timeframe can also help.&#x20;

</details>

<details>

<summary><strong>Why am I getting an "Internal Server Study" error?</strong></summary>

This error message appears when an user does not have access to the indicator. If you've already registered your TradingView username within our Accounts Dashboard and you're seeing this message, refresh your browser or app and make sure you're logged in on the TradingView profile you entered.

If you are still getting this issue, let our support team know your TradingView username, and we will fix your access. If you have not signed up with us, you'll see this error when trying to add our tools to your chart.

</details>

<details>

<summary><strong>Why are my candlesticks so tiny after adding the indicator?</strong></summary>

When your candlesticks (candles) suddenly look tiny or squished after adding an indicator on TradingView, it is almost always caused by an automatic scaling conflict. \[[1](https://www.tradingview.com/support/solutions/43000762934-my-chart-looks-compressed/)]

The indicator you added likely includes values, labels, or historical levels (like Pivot Points or a multi-timeframe moving average) that sit far away from the asset's current price. [TradingView](https://www.tradingview.com/support/solutions/43000762934-my-chart-looks-compressed/)'s "Auto Scale" feature forces the chart to fit *both* the entire price history and all indicator components onto the screen at once, compressing your candles into a flat line to make everything fit. \[[1](https://www.tradingview.com/support/solutions/43000473898-the-chart-looks-way-too-compressed/), [2](https://www.tradingview.com/support/solutions/43000762934-my-chart-looks-compressed/)]

Here is how to quickly fix the issue and get your candles back to normal size:

**Solution 1: Scale Price Chart Only (Most Common Fix)**

This forces TradingView to calculate the vertical height based strictly on the price candles, letting the indicator's far-away elements clip off the screen if necessary. \[[1](https://www.tradingview.com/support/solutions/43000762934-my-chart-looks-compressed/)]

1. Move your cursor over to the price scale axis on the far right side of your screen.
2. Right-click anywhere on that number column.
3. Check the box for Scale price chart only. Your candles should instantly pop back to their normal, readable size.&#x20;

**Solution 2: Unlink the Indicator from the Price Scale**

If the indicator does not need to sit directly on top of your candles, you can move it to its own independent scale. \[[1](https://www.tradingview.com/support/solutions/43000775579-indicator-moves-separately-or-is-not-attached-to-the-price/)]

1. Hover over the name of the problematic indicator in the top-left legend of your chart.
2. Click the three dots (More) icon next to it, or right-click the indicator line directly.
3. Hover over Pin to Scale.
4. Change it from *Pin to Scale A (Right)* to New price scale (Left or Right) or choose No scale. This untethers its visual boundary from your main candles. \[[1](https://www.tradingview.com/support/solutions/43000775579-indicator-moves-separately-or-is-not-attached-to-the-price/)]

**Solution 3: Move the Indicator to a Separate Pane Below**

If the indicator is meant to be read on its own (like an RSI, MACD, or volume profile), it shouldn't be shared with the main chart window. \[[1](https://www.tradingview.com/scripts/page-2/)]

1. Right-click the indicator line or name.
2. Select Move to -> New pane below or New pane above. \[[1](https://www.tradingview.com/support/solutions/43000775579-indicator-moves-separately-or-is-not-attached-to-the-price/)]

**Solution 4: Reset the Scale Automatically**

If the chart axis simply got jammed or dragged out of proportion while applying the indicator, a quick reset will fix it. \[[1](https://www.youtube.com/watch?v=yjZRxwv25Ys\&vl=en-US\&t=72)]

* Look at the bottom-right corner of your chart, right where the time axis meets the price axis. Click the Auto button (or press Alt + R on Windows / Option + R on Mac) to instantly re-center and auto-fit your candles

<br>

</details>

### Levels & Display

<details>

<summary><strong>Why are some levels visible on the 5m chart but not on the 1m chart</strong></summary>

***TradingView limits how far back historical data loads on lower timeframes.*** On a 1-minute chart, TradingView typically loads a shorter window of bar history than on a 5-minute or higher chart. Levels that formed outside that available history simply don't exist in the indicator's data on the 1m chart — they aren't hidden, the bars they formed on were never loaded.

If price moved to one of those areas on the 1m chart, the level would not be in the active pool and would not react. ***Switching to a higher timeframe where the full history is available is the best way to reference older structural levels.***

<br>

</details>

<details>

<summary><strong>Why do my levels look misaligned, stacked on top of each other, or not drawing correctly?</strong></summary>

</details>

<details>

<summary><strong>Can I backtest with LMS TradingView?</strong></summary>

**Backtesting support depends on TradingView's memory limits and your account.**

Some users are able to backtest using LMS TradingView without any issues, while others may encounter TradingView memory limitations that prevent the indicator from loading historical data.

Unfortunately, this behavior is controlled by **TradingView**, and there is currently no setting or workaround that guarantees backtesting will work for every account.

We are actively exploring ways to improve historical backtesting support in future updates. However, at this time, whether backtesting works will depend on TradingView's available resources and limitations for your account.

</details>

## Billing & Subscriptions

<details>

<summary><strong>How do I cancel my subscription?</strong></summary>

There are two ways to cancel your subscription depending on how you purchased it.

### Option 1: Membership Portal (Recommended)

1. Log in to your **IBLV Automated Dashboard**.
2. Open the **Membership Portal**.
3. Select **Manage Subscriptions**.
4. Complete the account authentication if prompted.
5. Select your active subscription and click **Cancel**.

***

### Option 2: Stripe Billing Portal

*Available only for subscriptions purchased with a credit or debit card through Stripe.*

1. Log in to your **IBLV Automated Dashboard**.
2. Open the **Stripe Billing Portal**.
3. Select your active subscription.
4. Click **Cancel Plan**.

***

### PayPal Subscriptions

If you purchased your subscription through **PayPal**, recurring billing is managed directly through your PayPal account.

To cancel your subscription:

1. Log in to your PayPal account.
2. Navigate to **Automatic Payments** or **Manage Automatic Payments**.
3. Locate your IBLV Automated subscription.
4. Cancel the recurring payment.

If you need assistance, please contact our support team.

</details>

<details>

<summary><strong>How do I change or upgrade my subscription?</strong></summary>

If you purchased through **Stripe**, you can change your subscription at any time.

1. Log in to your **IBLV Automated Dashboard**.
2. Open the **Stripe Billing Portal**.
3. Select your current subscription.
4. Click **Update Plan**.
5. Choose the monthly or yearly plan you'd like to switch to, or upgrade to another available product such as **LMS TradingView** or **LMS Edge**.
6. If you have a discount code, you can enter it during checkout.

Any remaining time on your current subscription will automatically be prorated toward your new subscription.

***

### PayPal Users

If your subscription was purchased through PayPal, you can manage it directly through your PayPal account.

If you'd like to change or upgrade your subscription and need assistance, please contact our support team.

</details>

<details>

<summary><strong>Do you offer refunds?</strong></summary>

IBLV Automated does **not** offer refunds except in cases where there is a verified issue with our software that prevents it from functioning as intended.

Refunds are **not** provided for:

* Failure to review the product requirements before purchasing.
* Setup or installation issues that can be resolved through our support resources.
* Data provider, broker, or third-party service issues.
* Change of mind after purchase.
* Failure to use the product during the subscription period.

If you're experiencing a technical issue, please contact our support team before requesting a refund. We're committed to helping you get your product up and running whenever possible.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iblvautomated.com/getting-started/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
