Troubleshooting

Bots trade Ecosystem markets, so a bot terminal must use eco. A custom screen left on the default spot asks the CEX for a market that does not exist there, gets [], and renders this exact panel. The stock bot terminal pins eco already; if you have built your own view, that is the first thing to check.

/api/exchange/chart returns whatever its cache holds and nothing more when the provider is unavailable — no error, no warning. For a market it has never cached, that is an empty array. Check the backend logs for the exchange module.

Ecosystem and futures candles come from ScyllaDB. If it is unreachable, those endpoints cannot answer. Everything else on the platform keeps working, which is why this presents as "one type of chart is empty" rather than as an outage.

A brand-new Ecosystem market has no history until it has traded. A thinly traded pair has gaps. Try a longer timeframe — a market with no 1-minute candles in the last two hours may still have daily bars.

If the host passes a concatenated symbol such as BTCFOO, the chart splits it by matching a known quote asset off the end — USDT, USDC, BTC, ETH, BNB, BUSD. An unlisted quote is passed through unchanged and then rejected by the endpoint's symbol validation. Pass the slashed form.

Opening a stock or FX instrument at an intraday timeframe used to produce a thin sliver of price against a wall of weekend and overnight void, because the opening window was sized from the clock rather than from the candles. Both edges are now derived from the candles themselves. If you still see it, you are on a build older than v6.0.0.

Flipping light and dark while looking at a chart clears the colour cache without forcing a repaint, so the chart keeps its current pixels until the next tick, pan, zoom or resize. On a live market that is under a second. On an idle chart — or in the admin design manager's preview — it persists until you touch it. Pan the chart one pixel and it corrects.

A saved theme is honoured on every page load, so this only affects live toggling.

Check the palette in Appearance & Design → Site Design. The chart reads those tokens directly, so a chart that disagrees with the site means the tokens themselves changed and something else is stale — a hard reload usually settles it.

Expected. A one-time cleanup removes stored indicator colours, and only colours, so un-customised indicators pick up the themed palette while a colour a user chose by hand is kept. Parameters and line widths are never touched.

Report it. Label text on badges, barriers, expiry strips and crosshair chips is derived from the fill it sits on rather than being hardcoded, so an unreadable combination means the palette itself has a contrast problem worth fixing in Site Design.

Chart Engine is not installed. The terminal falls back to TradingView, which cannot draw a strategy's levels. Install the addon and rebuild the frontend.

Mirrors are skipped rather than guessed. They are dropped when the chart's timeframe differs from the strategy's, when the user already has that indicator at that period, or when the chart does not implement it. The terminal opens on the timeframe the strategy declares precisely so the mirrors are eligible — changing the timeframe by hand will lose them.

Price-driven strategies such as grid and trailing stop declare no indicators at all, and there is nothing to mirror.

The bot claims to be running and has not produced a tick for more than 30 seconds. That is a bot problem, not a chart problem — the cockpit exists to surface it. Check the engine and the bot's last error, which the panel also reports along with how many times it has occurred.

Price has left the strategy's operating band, so the bot has nothing to do. It is running correctly and doing nothing, which is the honest thing for the chart to say.

The terminal polls its state every 15 seconds in addition to its socket, because the broadcast registry is per backend thread and a worker-thread deployment can drop events. Wait one poll, or press the refresh control in the header.