FLB Help

Troubleshooting

Start with the simplest signal.

Most FLB issues come from one of four states: account, machine, NinjaTrader, or chart. Work through them in that order.

01AccountMembership is active
02MachineControl Center is signed in
03NinjaTraderPackage loaded cleanly
04ChartIndicator and data are ready
Licensing & access

Access is missing or “Not Licensed” appears

Start in the Control Center for the platform where access is missing.

NinjaTrader 8

Check the Windows Control Center

  1. Open the Windows Control Center on the same PC as NinjaTrader 8.
  2. Confirm the correct FLB account and active membership.
  3. Open NinjaTrader and verify the product is installed and current.
  4. Confirm this PC owns the active machine seat, then restart NinjaTrader if prompted.
TradingView

Check the Web Control Center

  1. Open the Web Control Center and sign in.
  2. Go to Connections and confirm the exact TradingView username.
  3. Review the desired and actual grant status.
  4. Sync access, then check TradingView’s invitation-only scripts again.
NinjaTrader installation

The indicator is missing from the list

Open the Windows Control Center on the NinjaTrader PC, sign in, and use its NinjaTrader area to install or update the missing product. Restart NinjaTrader when the Control Center prompts you, then open a fresh chart and search the Indicators window for the FLB product name.

Do not manually import an FLB NinjaScript package. If a product was previously available, confirm you are using the same Windows installation, FLB account, and active machine seat.

Download the Windows Control Center →

Chart

The chart looks stale or incomplete

First confirm that live or historical data is reaching the chart. Then verify the instrument, session template, and timeframe expected by the indicator. Reload historical data only after checking those inputs; otherwise the reload repeats the same configuration problem.

For tools that build zones or profiles from a session or anchor, allow the required bars to load. A new workspace with limited history may not yet contain enough context.

Signals

A signal is not printing

Many FLB tools distinguish context, warning, confirmation, and regime. A chart can be working correctly without producing an actionable event. Compare the current market state with the guide’s setup and failure conditions before changing settings.

Check that the relevant visual toggle is enabled and that Trade Shield is not dimming or gating the state. Avoid lowering every filter simply to force more signals; that changes the question the tool is answering.

Connections & automation

The system is not ready for automation

Use HeartBeat and the Control Center to verify NinjaTrader, broker connection, strategy state, and the active machine. Confirm the correct account in simulation before reconnecting or restarting automation.

If an order may already exist, inspect the broker and NinjaTrader order state before taking any recovery action. Do not assume a disconnected interface means no live order exists.

Escalation

Open support in the Web Control Center

Sign in to the Web Control Center and choose Support to create a ticket or review an existing request. This is the support path for every member, including NinjaTrader users. Your ticket history and replies stay connected to the same FLB account.

Include the FLB product name, the exact message, when it started, your platform version, and whether the issue occurs on a fresh chart. Add a screenshot that includes the full chart and a short list of the steps already tried.

Faster answerProduct + exact error + screenshot + time
Open Control Center Support