3. FAQ & Troubleshooting

Answers to common questions and issues.

A stock symbol won't load

Equities are served by Massive or Alpaca, both of which require credentials. If a stock chart is empty or errors, confirm a key is configured for your mode:

• Frontend mode uses the browser keys (NEXT_PUBLIC_MASSIVE_API_KEY, or NEXT_PUBLIC_ALPACA_API_KEY_ID + NEXT_PUBLIC_ALPACA_API_SECRET_KEY, or keys entered in Settings → Data provider).
• Backend mode uses the server keys (MASSIVE_API_KEY, or ALPACA_API_KEY_ID + ALPACA_API_SECRET_KEY).

Equities prefer Massive, then fall back to Alpaca. Crypto pairs like BTCUSDT (Binance) and BTC-USDT (OKX) use public endpoints and need no key. See Configuring Providers & API Keys.

My data looks delayed

For Massive, the websocket feed can be realtime or delayed depending on your plan. Set it with MASSIVE_STOCKS_WS_FEED / NEXT_PUBLIC_MASSIVE_STOCKS_WS_FEED, or override per browser in Settings → Data provider → Massive → Streaming. Binance and OKX always stream live from public endpoints and have no delay option. See Realtime vs Delayed Data.

Which provider is a symbol using?

Resolution is automatic: crypto resolves to Binance first, then OKX; equities resolve to Massive first, then Alpaca. Force a specific provider with a query parameter (?provider=massive, ?provider=alpaca, ?provider=binance, or ?provider=okx) or a two-letter prefix (MA:, AL:, BI:, or OK:). For OKX perpetual swaps add the asset-class token: OK:FU:BTC-USDT-SWAP. See Symbols & Ticker Formats.

Why doesn't OKX appear in the symbol search when I type a Binance-style ticker?

OKX uses dash-separated instrument IDs (BTC-USDT) while Binance concatenates them (BTCUSDT). The symbol search normalizes both conventions, so typing either BTCUSDT or BTC-USDT will surface results from both providers. If OKX results are missing, try the OK: prefix (e.g. OK:BTC) to scope the search directly to OKX.

Are some volume indicators approximations?

Yes. Up/Down Volume, Net Volume, and Volume Delta infer direction from each bar's open/close, not from bid/ask aggressor side. ADR averages the chart bar's high-low range, so it equals the classic Average Daily Range only on daily bars. See the Built-in Indicator Library.

My custom indicator or strategy won't compile

For Pine Script v6 indicators and strategies, check the Limitations page for unsupported features (library import, multiline strings, etc.). For the legacy TypeScript engine, the authoring engine rejects import of values, async/await, returning a Promise from next(), and TypeScript namespace/decorators. See Authoring Language & Syntax (legacy).

useIndicator throws in my strategy

useIndicator is part of the legacy TypeScript strategy engine. Declare handles only in init(), then read them in next(). For Pine Script strategies use request.security or call ta.* functions directly — see Writing Strategies.

My backtest results seem off

Check the broker settings — commission, slippage, sizing, pyramiding, and the order-fill rules all change outcomes. Orders fill on the next bar by default. See Writing Strategies — Broker Configuration.

The assistant changed nothing

The assistant only proposes chart changes; you must click Apply on the action card. Read tools (observing the chart) run automatically, but write actions never mutate the chart until you approve them. See Applying AI Chart Actions.

I lost my watchlists / drafts / settings

Watchlists, strategy drafts, AI keys and conversations, saved layouts, and preferences are stored in your browser's local storage on a single device — they are not synced. They are removed if you clear site data. Use the watchlist export to back lists up and move them between browsers. See Workspace Preferences.

Where do API keys live, and is that safe?

AI provider keys, the Massive browser key, and the Alpaca browser key id + secret are stored in your browser's local storage. For browser-mode providers, requests go directly from your browser to the provider — which means the Alpaca secret is exposed to the browser (an accepted bring-your-own-credential tradeoff). Binance and OKX require no keys at all. Use minimally scoped, revocable keys, avoid shared machines, and prefer backend mode for equity-provider keys in public deployments. See Setting Up an AI Provider.

Next steps

That's the end of the guide. Head back to the start any time:

Next: Introduction