Troubleshooting: Connections, Market Data and Chart Issues

• Already subscribed (1029) — Rithmic answers rp_code 1029, “update bit type already exists”, when a subscription to the same instrument already exists on your login. The connection is fine; the stream is held elsewhere, most often by a second copy of Senzoukria or another platform on the same login.
• Bridge drift badge — The drift badge appears when NinjaTrader announced more historical ticks than the bridge delivered to Senzoukria. Tick-based bars such as 100T may not align bar for bar with NinjaTrader for that session; reconnecting retries the history.
• History load already running — Only one history load can run per instrument at a time. When a second chart or window asks for the same contract, Senzoukria waits, retries once after 3 seconds, and then tells you to reload history if the other load still holds it.
• Subscription required or expired — The desktop app checks the licence at sign-in and at every renewal of the session. Without an active PRO subscription the server refuses it, and the app says whether the subscription is missing, expired or the licence suspended.
• GEX key required — GEX and Option Flow open only when an options data key is available. In 0.45.0 the screen asked for Alpaca keys even when a Tradier token was saved; 0.46.0 accepts any options key (Tradier, Alpaca, Market Data for GEX) and shows “Options data key required” only when none exists.
• Alpaca unauthorized — Alpaca keys are stored in Senzoukria without an online test, so a wrong key only fails when GEX or Option Flow asks Alpaca for data. The failure shows as “Alpaca unauthorized (HTTP 401/403) — check your API keys”; a rate limit shows as HTTP 429.
• Anthropic refused this key — Senzoukria tests a Claude API key with Anthropic before saving it. A 401 or 403 answer means the key is refused and it is not saved; a network problem or an Anthropic outage saves the key but says it was not verified.
• NinjaTrader bridge stuck connecting — When the Senzoukria footprint stays on “Bridge: connecting to NinjaTrader on 127.0.0.1:7272…”, nothing is listening on that local port: NinjaTrader is closed, the OrderflowBridge indicator is not on a chart, or its port differs from 7272.
• Databento book refused — With Databento CME as the heatmap source, the order book comes from Databento’s live mbp-10 schema on your own key. When Databento refuses it, Senzoukria stops that stream and shows Databento’s wording, such as “Not authorized for mbp-10 schema”, instead of an empty map.
• Crypto DOM Profile: no live depth — On crypto footprints, the DOM Profile and the liquidity walls disappear during an order book gap, and a notice names the book state. After the backend gives up, the notice turns red with a timed Retry.
• Python engine unavailable — Python scripts in Senzoukria need an engine downloaded once from senzoukria.com and then run offline. “Engine unavailable” means it did not start; JavaScript scripts are unaffected. A separate message warns when a script’s declared language does not match its code.
• Accepted but no data — When the connection diagnostic passes gateway, system, login and subscription but no tick arrives, Senzoukria says so instead of blaming an entitlement: a closed market, an expired contract, a second session on the login or an unprovisioned login all look the same on screen.
• History could not be completed — After two consecutive history downloads that bring nothing back, a Senzoukria chart says so. With broker codes, it prints them unchanged; with no code at all, the usual meaning is an empty archive on that Rithmic system.
• History shorter than requested — When Rithmic serves a history window without error but with no ticks, its archive does not reach further back for that contract and account. Senzoukria reports how many days it really loaded against the range you asked for.
• Crypto history incomplete — Crypto charts in Senzoukria build history in steps: candles, then bid × ask rebuilt from Binance trade archives, then chart bars. After 5 minutes on Binance the chart shows what is available and keeps loading; missing pieces are named, never filled in silently.
• History loading stalled — If a history download sends no progress for 120 seconds, Senzoukria stops waiting, closes the loading gauge on what the cache and the live feed already have, and says “History loading stalled”. Reload history restarts the download.
• Invalid email or password — The desktop app signs in with the email and password of your Senzoukria web account. “Invalid email or password.” means the licence server did not accept that pair; repeated failures can lock the account for a few minutes.
• Databento needs a live licence — Senzoukria measures what your Databento key can open before letting a module use it. A module switch stays disabled with “Needs a live {dataset} licence on your Databento plan” when the dataset it requires is not live on your key.
• Replay: no broker credentials saved — Replay downloads a session that is not on disk from Rithmic history, with the credentials of your default Rithmic connection. With no such profile or no saved password, the load fails with “no broker credentials saved”; sessions on disk and imported sessions still replay.
• No local data for this instrument — A Senzoukria chart can open offline only on history already downloaded to the machine. For an instrument never loaded before, there is nothing to draw until the first broker connection fills the cache; another instrument may still open offline.
• No loss-side exit received — The protections stage of the trading desk counts a stop only when the broker lists it among the working orders with the position’s full quantity. “No loss-side exit received” means no such order was reported; “exit quantity to check” means one exists but its quantity differs.
• No market depth received (crypto) — On Binance and Bybit pairs, Senzoukria raises “No market depth received” when the order book subscription was accepted but no book arrived within 15 seconds. The notice is a local diagnosis, not an exchange refusal, and offers a Retry that subscribes again.
• Replay: no ticks for this day — When the history download of a Replay day returns no tick at all, Senzoukria refuses to open an empty session and says “no ticks for {day} — market closed that day, or nothing archived”, with the broker codes it received.
• NT misconfigured banner — The orange “NT misconfigured” banner means the NinjaTrader bridge sends ticks without a sequence counter: the indicator is older than v2 or Tick Replay is off on the chart. 100-tick bars will not align with NinjaTrader until you fix it upstream and reconnect.
• Order book feed stopped — When the backend cannot resynchronize a crypto order book after its bounded reconnection attempts, Senzoukria stops showing the last known book as live and says “Order book feed stopped”. Retry becomes available after a short delay and opens a new subscription.
• Replay load refused (rp_code 13) — A Replay session that is not on disk is downloaded tick by tick from Rithmic’s history. When the broker answers rp_code 13 during that download, Senzoukria stops and says the broker denies tick history on this account; a history login refusal has its own message.
• Connect needs a saved password — A Rithmic connection profile without a saved password cannot connect, and the Test connection button needs the password typed again because the stored one never leaves the keychain. Edit the profile, type the password, then save or test.
• Script stopped after 2000 ms — Every Senzoukria script runs in a sandboxed worker with a budget of 2 seconds per run. A script that exceeds it is stopped with “script stopped after 2000 ms (infinite loop?)”; a sandbox that never started reports a different message.
• Sign in in the main window — Detached Senzoukria windows share the session of the main window. When no session exists, a detached chart shows “Sign in in the main window to open charts.” and other detached modules ask you to sign in there and reopen the view.
• Credentials not saved — With “Save my credentials” ticked, Senzoukria stores your password in the operating system keychain. If that write fails, you are still signed in, and the app shows the real error for a moment instead of pretending the credentials were saved.
• News source rate-limited — The Senzoukria news wire comes from GDELT, a free open-data feed that allows about one request every few seconds per IP. When it throttles, the app stops calling for a while and says how long, instead of retrying and extending the ban.
• Import stopped: memory limit — The Senzoukria Databento importer holds trades in memory until each day is complete. When too many open days accumulate across contracts, it stops with “Stopped: memory limit reached”. Sessions already complete are kept; import fewer contracts at a time.
• System name not on the gateway — Rithmic answers rp_code 1067 when the system name you typed is not served by the gateway you connect to. Senzoukria fetches the gateway’s own list and prints it, so you can pick the exact system your account lives on.
• History refused (rp_code 13) — This chart notice means Rithmic answered some history windows with rp_code 13. Measured on a real account, these refusals were intermittent while logins were accepted; the chart keeps running on cached and live data and retries by itself.
• Subscription refused — This notice means the Rithmic login went through but the market data subscription for that contract came back refused. Senzoukria lists the possible causes by frequency, keeps the broker’s exact wording, and never presents one cause as certain.
• Bubble rebuild refused — The bubble rebuild of Senzoukria asks Rithmic for tick history again to recreate past Big Trades bubbles. When the broker answers rp_code 13, nothing can be rebuilt beyond that point; candles already in the cache do not move.
• Chart could not start — A Senzoukria chart pane that has not mounted after 15 seconds shows “The chart could not start.” with a “Retry this chart” button; a detached chart window that is not created within 15 seconds reports “Could not open: The window is not responding.”
• Provider unavailable — When a Replay history request gets no answer while the CME is open, Senzoukria shows “Provider unavailable”: no new history can be downloaded right now, the cache is untouched, and the request goes through again once the provider answers.
• Gateway did not answer — When the first step of the Senzoukria connection diagnostic fails, no WebSocket session could be opened to the Rithmic gateway: a wrong URL, a colocation-only access point, or a firewall, VPN or proxy on the way. Nothing about the account has been tested yet.
• Heatmap could not start (EvalError) — In Senzoukria 0.45.0 the installed app could show “The heatmap could not start” with an EvalError about ‘unsafe-eval’ and the Content Security Policy. The rendering library generated code at run time, which the app’s security policy forbids. Version 0.46.0 replaces it; update to 0.46.0 or later.
• Market closed, nothing new — Outside CME trading hours no tick is published, so Senzoukria has no new history to download. It says so in the chart and in Replay, and keeps everything already cached available for scrolling, computing and replay.
• Report could not be sent — The Report a problem screen of Senzoukria sends your description with a measured technical context. If the server cannot be reached, nothing is sent; if too many reports left the machine recently, it asks you to wait a few minutes.
• Sign-in server unreachable — When the desktop app cannot reach the licence server, the sign-in fails with a network message that asks you to keep your password: a network error says nothing about your credentials, and resetting the password would not help.
• Account signs in with Google — A Senzoukria account created with Google has no password, and the desktop app cannot sign in with Google directly. Set a password on the website with “Forgot password?”, then sign in to the app with that email and password.
• Price grid unknown — When Senzoukria does not know an instrument’s tick size, the history download still works but nothing is cached, so the whole window is downloaded again each time the chart opens. The chart looks normal; the notice is the only sign.
• Maximum number of machines — Each Senzoukria licence allows a set number of machines. When all slots are taken, a new machine is refused at sign-in. Free a slot from the website’s devices page, then sign in again.
• This screen stopped — When a screen of Senzoukria throws an error while drawing, only that zone is replaced by a “This screen stopped” card; the rest of the app, your data and your broker connection keep running. Reload restarts the screen, and Copy the details gives support the error.
• Tradier token check failed — Senzoukria tests a Tradier token online before saving it, by requesting a SPY quote from Tradier’s production API. If Tradier refuses, the token is not saved and the error starts with “token check failed”.
• Trading disabled on the connection — Senzoukria refuses to place or modify an order when the connection profile has its Trading toggle off, which is the default on funded accounts. Cancelling orders and flattening stay allowed because they only reduce risk.
• Local data, not live — With no broker connected, a Senzoukria chart opens on the history already stored on the machine and wears a “Local data” badge. It scrolls and computes as usual but does not advance; live ticks, the order book and the bar in progress need a broker.
• AI model unreachable — The model picker of the Senzoukria assistant tests the engine you choose. “Unreachable” means it did not answer, without saying whether the key, the network or the engine is at fault; the raw answer is shown under it. Local engines must run on this machine, and Groq keys are tested before use.
• Backtest import from Databento — The automatic backtest imports a Databento folder under one contract root as a continuous series: trades give bars with delta and price levels, ohlcv-1m gives bars without them. A folder with neither is refused, roll days are left out, and bars already cached are never replaced.
• Big Trades not showing — The Big Trades bubbles of the Senzoukria footprint only draw in candle view, only from trades actually received, and pause when the view holds too many of them. A short line on the chart says which of the three applies.
• Diagnostic: session already running — The Senzoukria connection diagnostic opens its own Rithmic session, so it refuses to run while a market data session is live on the same login. It also reports what the server did during the test, such as a forced logout or a refused order-by-order depth.
• DBN parent symbol not imported — Senzoukria does not import DBN files requested with a parent symbol such as MNQ.FUT, or with instrument IDs only: without the instrument definitions, a contract cannot be told apart from a spread. Export them again with contract symbols, a continuous symbol, or as CSV with symbols.
• Databento file names without a date — Senzoukria checks which days an export covers from the dates in Databento’s file names. A renamed file without a date cannot be checked, so it is not imported; keep names such as glbx-mdp3-20250910.trades.csv.
• Databento files set aside — Before importing, Senzoukria scans the whole Databento folder and lists the files it will not use, grouped by reason: unsupported format, Databento metadata, unreadable or empty, password-protected archive, refused for safety, or beyond the scan limits. Nothing is imported before you confirm, and your files are never modified.
• Databento sessions not written — Senzoukria writes an imported Replay session only when it is complete and unambiguous. A session is not written when the previous day’s file is missing, the day’s own file is missing, two files carry the same contract, it exceeds the Replay limit, or the disk write fails.
• DOM: aggregated L2 only — On a Rithmic DOM, the MBO badge tells whether the full order-by-order book is active. When it is grey, the ladder is limited to the aggregated levels the feed publishes. A separate age indicator turns red after 3 seconds without a depth update.
• dxFeed: no order book — On the dxFeed source, Senzoukria receives trades only: no order book is requested, so the DOM and the heatmap stay empty by design. The dxFeed demo endpoint runs about 15 minutes behind the market, and the connection form says so.
• Free Rithmic demo refused — A free 14-day Rithmic demo with live market data cannot log in to Senzoukria: Rithmic does not offer the R | Protocol API that the app speaks to demo accounts. A prop-firm evaluation or a broker account with a paid market data subscription is required.
• GEX delayed or stale — The GEX status chip in Senzoukria says how old the option chain is and whether the source publishes with a delay. LIVE appears only for a dated, fresh chain from a real-time source; delayed sources, chains older than 20 minutes and undated chains are labelled as such.
• GEX no data or provider error — NO DATA means no option chain has been received and the last request failed; PROVIDER ERROR means a chain is on screen but the last request failed, so what you see came from before. The tooltip carries the provider’s error.
• Heatmap graphics context lost — Senzoukria measures whether its heatmap is still being painted. “Graphics context lost” means the WebGL context was dropped and the map will not come back on its own; “Rendering has been stopped” means data still arrives but nothing is painted, so the screen is a frozen image.
• Heatmap empty, feed live — Three Senzoukria banners explain an empty heatmap when the renderer is working: no order book received for some seconds, a colour scale that was never calibrated, or a displayed window that falls outside the retained history. Each has a different fix.
• Liquidity tracker unavailable — The Liquidity tracker of the Senzoukria heatmap follows each order’s life to tell withdrawn liquidity from executed liquidity. It needs the order-by-order (MBO) feed, which only Rithmic provides, so its switch is disabled on other sources.
• No update prompt — Senzoukria checks for a newer version at start-up, unless a version is pinned on the Versions card or the app runs from sources. A pinned version shows “Automatic updates are off while a version is pinned.”; one click resumes them.
• Order cells disabled (price) — Senzoukria disables price-based order cells when it has no trustworthy price: no price seen yet, no qualified best bid and ask, or no new price for 15 seconds. It refuses to guess a price from an old trade.
• Max order size guard — Senzoukria refuses any order larger than the Maximum order size you set in Settings → Trading. The guard is enforced in the backend for every order entry of the app; leave the field empty for no cap.
• Quantower bridge not connecting — The Quantower bridge feeds Senzoukria from a running Quantower chart over 127.0.0.1:7273. A banner stuck on connecting means Quantower or its bridge add-on is not running; an orange “QT misconfigured” banner means ticks arrive without a sequence counter.
• Replay order refused (L1) — In a Replay session that carries its best bid and ask (imported from Databento mbp-1 with the L1 kept), simulated orders fill at the bid or ask, never at the last trade. When that side is empty, not yet received or lost, the order is refused and the message says which.
• Replay load stopped responding — A Replay load reports progress while it downloads. If no progress arrives for 90 seconds, Senzoukria abandons the wait and says the backend stopped responding. Other short messages cover a load already running and a replay that reached its end.
• Rithmic login refused (rp_code 13) — When Rithmic answers a Senzoukria login with rp_code 13 “permission denied”, the account is refused on that system for the R | Protocol API; the code does not say which layer refused it. The app lists the causes to check, cheapest first, and never treats it as a rights verdict.
• Heatmap waiting for the order book — The Senzoukria heatmap only starts drawing once it receives a first order book with both a bid and an ask side. Until then its status line reads “{symbol} · waiting for the first order book”. The cause depends on the source: a closed market, depth not served, a bridge not live, or a crypto book that never arrived.
• Update install failed — Senzoukria verifies every installer’s signature before running it. An update can fail in the startup prompt (“Install failed: …”) or on the Versions card, which names the reason: no signature published, signature mismatch, download error, or a platform where in-app installs are not available.
• ThetaData terminal not detected — ThetaData has no remote API: you run their Theta Terminal on your own machine and Senzoukria reads it on localhost. “Terminal not detected” or “Theta Terminal unreachable on … — is ThetaTerminal.jar running?” means nothing answers there.
• Trading desk: no account feed — The Senzoukria trading desk lights its four stages (connection, account, position, protections) only from what the broker actually reports. “No connection ready”, “No account feed” and “Feed error” each point to a different step to check before any order can be routed.

This page in other languages

• Français
• Español
• Italiano
• Русский
• 中文
• العربية